Data processing method for pushing data recall, related equipment and storage medium
Through automated matching of push rules and analyzing whiteboard data, the problem of push data not being output in the specified bit is solved, the inspection efficiency is improved and the cost is reduced, and automated inspection and accurate screening is realized.
Patent Information
- Application Number
- CN202310518106.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2043-05-09
AI Technical Summary
The existing technology is inefficient and costly when troubleshooting push data is not output in the corresponding push bit or cannot recall push data, and mainly relies on manual analysis of whiteboard data.
By responding to the data push test request of the specified push bit, the whiteboard data generated during the recall process of the push data from the push database to the specified push bit is obtained, and the target push rules matching the specified push bit are obtained from multiple push rules. Match the data key fields. If the semantics do not match the target push rules, generate a recall diagnosis result to prompt that the push data is not pushed to the specified push bit logic.
It realizes automated troubleshooting of reasons why push data cannot be recalled, improves problem-solving efficiency, reduces time and labor costs, avoids the need to manually analyze whiteboard data, and improves troubleshooting efficiency by accurately filtering suitable push rules.
Smart Images

Figure CN118939862A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer and communication technology, and in particular to a data processing method for push data recall, a data processing device for push data recall, an electronic device, a computer-readable storage medium, and a computer program product. Background Art
[0002] At present, the methods for troubleshooting the problem that the pushed data is not output in the corresponding push position (that is, the pushed data cannot be output or the pushed data cannot be recalled) mainly include: first, the debugging personnel manually obtain the whiteboard data, and then the debugging personnel analyze the whiteboard data based on their own experience to find out the reason why the pushed data cannot be recalled. It can be seen that the current troubleshooting process is basically all done manually, resulting in low troubleshooting efficiency and high troubleshooting costs. Therefore, how to improve the efficiency of problem troubleshooting and reduce the troubleshooting cost when the pushed data cannot be recalled is a problem that needs to be solved urgently. Summary of the invention
[0003] The embodiments of the present application provide a data processing method for push data recall, a data processing device for push data recall, an electronic device, a computer-readable storage medium, and a computer program product, which can improve the efficiency of problem troubleshooting and reduce the troubleshooting cost when the push data cannot be recalled.
[0004] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.
[0005] According to one aspect of an embodiment of the present application, a data processing method for push data recall is provided, including:
[0006] In response to a data push test request for a designated push location, the whiteboard data generated during the recall process of the push data from the push database to the designated push location is acquired through the push service platform;
[0007] Acquire a target push rule matching the designated push position from a plurality of push rules through a diagnostic platform; different push rules indicate different push logics;
[0008] Acquire key data fields in the whiteboard data that match the target push rule;
[0009] If the semantics of the key field of the data does not match the push logic indicated by the target push rule, it is determined that the pushed data is not pushed to the designated push location, and a recall diagnosis result that the pushed data is not pushed to the designated push location is generated according to the push logic indicated by the target push rule;
[0010] Outputting the recall diagnosis result of the pushed data; the recall diagnosis result is used to prompt that the pushed data is not pushed to the push logic that is not satisfied by the designated push location.
[0011] According to one aspect of an embodiment of the present application, a data processing device for push data recall is provided, the device comprising an acquisition unit, a processing unit and an output unit, wherein:
[0012] The acquisition unit is used to respond to a data push test request for a designated push location, and acquire the whiteboard data generated during the recall process of the push data from the push database to the designated push location through the push service platform;
[0013] The processing unit is used to obtain a target push rule matching the specified push position from a plurality of push rules through a diagnostic platform; different push rules indicate different push logics;
[0014] The processing unit is further used to obtain the key data field in the whiteboard data that matches the target push rule;
[0015] The processing unit is further configured to determine that the pushed data is not pushed to the designated push location if the semantics of the key field of the data does not match the push logic indicated by the target push rule, and generate a recall diagnosis result that the pushed data is not pushed to the designated push location according to the push logic indicated by the target push rule;
[0016] The output unit is used to output the recall diagnosis result of the pushed data; the recall diagnosis result is used to prompt that the pushed data is not pushed to the push logic that is not satisfied by the designated push position.
[0017] In one embodiment of the present application, when the processing unit obtains a target push rule that matches a designated push position from multiple push rules through a diagnostic platform, it can be specifically used to: obtain push range information of the designated push position through the diagnostic platform; wherein the push range information includes at least one of the following: associated push data of the designated push position, push position information of the designated push position, application identification information of the application to which the designated push position belongs, and environment identification information of the initiation environment of the data push request initiated by the designated push position; obtain candidate push rules from multiple push rules, and adaptation range information of the candidate push rules; if the adaptation range information of the candidate push rule matches the push range information, the candidate push rule is determined as the target push rule.
[0018] In one embodiment of the present application, multiple push rules are arranged in a preset order; when the processing unit obtains a target push rule that matches a specified push position from multiple push rules through a diagnostic platform, it can be specifically used to: obtain push range information of the specified push position through the diagnostic platform; select push rules in sequence according to the arrangement order of the multiple push rules, and match the adaptation range information of the selected push rules with the push range information until the adaptation range information of the selected push rule matches the push range information; use the push rule whose adaptation range information matches the push range information as the target push rule.
[0019] In one embodiment of the present application, the processing unit can be further used to: splice the data key field with the target push rule to obtain a spliced text; perform semantic correlation recognition processing on the spliced text to obtain the semantic correlation between the data key field and the target push rule; if the semantic correlation is less than or equal to a preset correlation threshold, it is determined that the semantics of the data key field does not match the push logic indicated by the target push rule.
[0020] In one embodiment of the present application, multiple push rules are arranged in a preset order; the processing unit can be further used to: if the semantics of the data key field matches the push logic indicated by the target push rule, then the push rule that is arranged after the target push rule and matches the designated push position is used as the new target push rule; obtain a new data key field in the whiteboard data that matches the new target push rule; when the semantics of the new data field does not match the push logic indicated by the new target push rule, determine that the push data is not pushed to the designated push position, and generate a recall diagnosis result for the push data according to the push logic indicated by the new target push rule.
[0021] In one embodiment of the present application, the acquisition unit can be further used to: acquire object identification information of a specified object, and push position information of a specified push position; search an object request database for historical data push requests initiated by a specified object through a specified push position based on the object identification information and the push position identification information; wherein the object request database is used to store historical data push requests initiated by multiple objects through multiple push positions; and generate a data push test request based on the found historical data push requests.
[0022] In one embodiment of the present application, the acquisition unit can be further used for: if the historical data push request initiated by the specified object through the specified push position is not found in the object request database, then obtaining a data push request matching the push position identification information from an online request database for storing historical data push requests initiated through multiple push positions; wherein the obtained data push request is used to obtain push data for the specified push position; and based on the obtained historical data push request, generating a data push test request.
[0023] In one embodiment of the present application, when the acquisition unit generates a data push test request based on the found historical data push request, it can be specifically used to: convert the data format of the found historical data push request into a target data format to obtain a converted data push request; modify the parameters of the target field in the converted data push request to preset debugging parameters to obtain a modified data push request; and generate a data push test request based on the modified data push request.
[0024] In one embodiment of the present application, when the acquisition unit generates a data push test request based on the modified data push request, it can be specifically used to: obtain the push service type to which the specified push position belongs; based on the pre-established correspondence between the push service type and the request protocol, obtain the request protocol corresponding to the push service type; based on the request protocol, process the modified data push request to generate a data push test request.
[0025] In one embodiment of the present application, the data processing device for push data recall also includes a request initiating unit, which can be used to: obtain the push service type to which the specified push position belongs; based on a pre-established correspondence between the push service type and the request protocol, obtain the request protocol corresponding to the push service type; based on a pre-established correspondence between the request protocol and the package sending protocol, obtain the package sending protocol corresponding to the request protocol; based on the package sending protocol, initiate a data push test request.
[0026] In one embodiment of the present application, when the acquisition unit responds to a data push test request for a designated push position and acquires the whiteboard data generated during the recall process of the push data from the push database to the designated push position through the push service platform, it can be specifically used to: send the data push test request to the push service platform so that the push service platform acquires the package sending protocol corresponding to the designated push position, initiates a data push test request based on the package sending protocol, and the push service platform acquires the whiteboard data; and receives the whiteboard data returned by the push service platform.
[0027] In one embodiment of the present application, when the output unit outputs the recall diagnosis result of the pushed data, it can be specifically used to: if the data push test request carries proxy processing information, the recall diagnosis result of the pushed data is sent to the proxy processing platform, so that the proxy processing platform obtains a push request modification method that matches the recall diagnosis result of the pushed data, and modifies the data push request initiated by the specified push position according to the push request modification method.
[0028] According to one aspect of an embodiment of the present application, an embodiment of the present application provides an electronic device, comprising one or more processors; a storage device for storing one or more computer programs, when the one or more computer programs are executed by the one or more processors, the electronic device implements the data processing method for push data recall as described above.
[0029] According to one aspect of an embodiment of the present application, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor of an electronic device, the electronic device executes the data processing method for push data recall as described above.
[0030] According to one aspect of an embodiment of the present application, an embodiment of the present application provides a computer program product, including a computer program, wherein the computer program is stored in a computer-readable storage medium, and a processor of an electronic device reads and executes the computer program from the computer-readable storage medium, so that the electronic device performs the data processing method for push data recall as described above.
[0031] In the technical solution provided by the embodiment of the present application, by judging whether the semantics of the key data fields in the whiteboard data match the push logic indicated by the target push rule, when the semantics of the key data fields do not match the push logic indicated by the target push rule, the recall diagnosis result of the push data can be directly generated according to the push logic indicated by the target push rule. It can be seen that the embodiment of the present application can autonomously find out the reasons why the push data cannot be recalled, avoiding the scenario where the whiteboard data needs to be manually analyzed to troubleshoot the problem, greatly improving the efficiency of problem troubleshooting, and reducing the time, labor and other troubleshooting costs. At the same time, the embodiment of the present application will screen a plurality of push rules to a certain extent, and only the push rules that match the specified push position will be used as the target push rules for the next step of judgment; avoiding the situation where multiple fields in the whiteboard data need to be logically compared one by one with multiple push rules. Therefore, the embodiment of the present application can further improve the troubleshooting efficiency by accurately screening out the target push rules suitable for the specified push position.
[0032] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:
[0034] Figure 1 It is a structural diagram of a data processing system for push data recall provided in an embodiment of the present application;
[0035] Figure 2 It is a flowchart of a data processing method for push data recall shown in an exemplary embodiment of the present application;
[0036] Figure 3 It is a flowchart of another data processing method for push data recall shown in an exemplary embodiment of the present application;
[0037] Figure 4 It is a structural diagram of a rule engine module provided in an embodiment of the present application;
[0038] Figure 5A is an interface schematic diagram of a push configuration interface shown in an exemplary embodiment of the present application;
[0039] Figure 5B is a schematic diagram of a display interface for recalling diagnostic results shown in an exemplary embodiment of the present application;
[0040] Fig. 6A It is a schematic diagram of a display interface for recalling diagnosis results of multiple push data shown in an exemplary embodiment of the present application;
[0041] Figure 6B It is a schematic diagram of an interface showing the filtering reasons in a rough sorting stage according to an exemplary embodiment of the present application;
[0042] Figure 6C It is a schematic diagram of an interface of filtering reasons in a fine sorting stage shown by an exemplary embodiment of the present application;
[0043] Figure 7 It is a flowchart of another data processing method for push data recall shown in an exemplary embodiment of the present application;
[0044] Figure 8 It is a structural diagram of another data processing system for push data recall provided in an embodiment of the present application;
[0045] Fig. 9 It is a flowchart of another data processing method for push data recall shown in an exemplary embodiment of the present application;
[0046] Fig.10 is a schematic diagram of a process of generating a data push test request shown in an exemplary embodiment of the present application;
[0047] Fig.11This is a schematic diagram of a process of obtaining a data return packet shown in an exemplary embodiment of the present application;
[0048] Fig.12 is a structural block diagram of a data processing device for push data recall shown in an exemplary embodiment of the present application;
[0049] Fig.13 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION
[0050] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.
[0051] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0052] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all contents and operations, nor must they be executed in the order described. For example, some operations may be decomposed, while some operations may be combined or partially combined, so the actual execution order may change according to actual conditions.
[0053] It should also be noted that the "multiple" mentioned in this application refers to two or more than two. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship.
[0054] Websites, platforms, applications (Application, APP) and other application software will insert certain push data based on their own application functions to recommend items to the objects using the corresponding application software. Therefore, there will be push positions for displaying push data in some interfaces of these application software.
[0055] The recall process of pushed data refers to the process of pushing data from the push database to the push position. Among them, the push database refers to the database used to store push data, and the push database can store multiple push data. In the recall process, the push data needs to go through the screening of various modules in the push system, such as directional matching, mixed / rough sorting, fine sorting, and push data filling. As long as there is a mismatch in any module, the push data will be filtered and will eventually fail to reach the push position for output. This situation is called push data failure or failure to recall push data.
[0056] In the related art, the method for troubleshooting the reason why the pushed data cannot be recalled is mainly: first manually log in to the server that stores the data push request to retrieve the data push request for the push position, and then manually modify the data push request to the debugging state. After that, the debugger resends the modified data push request so that the corresponding server responds to the modified data push request and obtains the push reply package containing the whiteboard data. Among them, the whiteboard data includes the processing data of the pushed data during the recall process. Specifically, the whiteboard data includes the detailed processing data of the pushed data coming out of the push database, and the modules in the push system such as directional matching, mixed / rough sorting, fine sorting and push data filling process the pushed data. Finally, the debugger troubleshoots the reason why the pushed data cannot be recalled by analyzing the whiteboard data. The above schemes are basically all completed manually, resulting in low troubleshooting efficiency and high troubleshooting costs.
[0057] Based on this, the embodiment of the present application provides a data processing solution for recalling push data, which pre-sorts out multiple push rules; then, it responds to the data push test request for the specified push position and obtains the whiteboard data corresponding to the push data through the push service platform. At the same time, the target push rule that matches the specified push position can also be obtained from the above multiple push rules through the diagnostic platform, so that when the data key field in the whiteboard data does not match the push logic indicated by the target push rule, a recall diagnostic result that the push data is not pushed to the specified push position is generated according to the push logic indicated by the target push rule.
[0058] Among them, the data push test request refers to the data push request that has been modified to the debugging state, that is, the data push test request contains debug = true. In addition, it may be stipulated that certain push positions can only display certain push data, and the push positions in certain applications do not need to be matched in a targeted manner, etc., resulting in some push rules not being applicable to the specified push positions. Therefore, it is necessary to obtain the target push rule that matches the specified push position. The data key field in the whiteboard data refers to the field in the whiteboard data that matches the target push rule.
[0059] In addition, the push service platform is used to recall the push data, that is, to determine the push data that is finally output at the push position from the push data in the push database. Specifically, the push service platform is equivalent to the aforementioned push system, including modules such as directional matching, mixed / rough sorting, fine sorting, and push data filling. The push service platform can process and filter the push data through these modules, and record the processed data of each module to form whiteboard data.
[0060] In addition, the diagnostic platform can be used to store multiple push rules, and can also be further used to analyze the recall diagnostic results of push data through multiple push rules. Different push rules indicate different push logics. The various push rules can be obtained by sorting and analyzing the processing logic of each module such as different directional matching, mixed / rough sorting, fine sorting, and push data filling, or by summarizing the debugging personnel's experience in analyzing whiteboard data, without limitation. For example, due to directional matching, push data that does not match the corresponding direction will be filtered out, resulting in the inability to recall the push data. Therefore, the push logic indicated by the push rule can be: push data matches direction A, and the push data is added to the push data queue of the next processing module.
[0061] At the same time, the recall diagnosis result is used to prompt the push logic that the push data is not pushed to the designated push position. The whiteboard data includes the processing data of the push data during the recall process; and the key data fields in the whiteboard data that match the target push rules refer to the fields in the whiteboard data that have a high similarity with the target push rule text. Specifically, the whiteboard data includes the processing data of each module during the recall process, which is equivalent to recording the detailed process of the push data being processed by each module. Among them, the whiteboard data can specifically include which directions the push data does not match, which directions match, which push data queues it enters, which push data queues are filtered by, and the reasons for filtering, etc.
[0062] Therefore, if the semantics of the key fields of the data do not match the push logic of the target push rules, it means that the push data is filtered in the processing module corresponding to the push logic indicated by the target push rules, resulting in the push data not being pushed to the push position; then, the recall diagnosis result of the push data can be directly analyzed according to the push logic indicated by the target push rules.
[0063] It is not difficult to see that this solution can generate a recall diagnosis result of the push data directly according to the push logic indicated by the target push rule when the semantics of the key fields of the data do not match the push logic indicated by the target push rule by judging whether the key fields of the data match the push logic indicated by the target push rule. It can be seen that this solution effectively avoids the scenario where manual analysis of whiteboard data is required to troubleshoot problems, which is conducive to improving the efficiency of problem troubleshooting and reducing the cost of troubleshooting. At the same time, this solution will perform certain screening on multiple push rules, and only the push rules that match the specified push position will be used as the target push rules for the next step of judgment; it avoids the situation where multiple fields in the whiteboard data need to be logically compared with multiple push rules one by one. Therefore, this solution can further improve the troubleshooting efficiency by accurately screening out the target push rules suitable for the specified push position.
[0064] Based on the above-mentioned data processing scheme for push data recall, the present application embodiment provides a data processing system for push data recall, which can be found at Figure 1 , Figure 1 The data processing system for push data recall shown may include multiple terminal devices 101 and multiple servers 102. Among them, a communication connection is established between any terminal device and any server. For example, the terminal device 101 may include any one or more of a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart car-mounted device, and a smart wearable device. Multimedia playback clients, social clients, browser clients, information stream clients, educational clients, etc. can be run in the terminal device 101. The server 102 can be a server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms. Any terminal device 101 and any server 102 can be directly or indirectly connected in communication via wired or wireless communication, and this application is not limited here.
[0065] In some embodiments, the above-mentioned data processing method for pushing data recall may only include: Figure 1The server 102 in the data processing system for push data recall shown is executed, and the specific execution process is: the server 102 can respond to the data push test request for the designated push position, and obtain the whiteboard data generated in the recall process of the push data from the push database to the designated push position through the push service platform. Then, the server 102 can obtain the target push rule that matches the designated push position from multiple push rules through the diagnostic platform. After that, the server 102 can obtain the data key field that matches the target push rule in the whiteboard data. If the server 102 determines that the semantics of the data key field does not match the push logic indicated by the target push rule, the server 102 can determine that the push data is not pushed to the designated push position, and generate a recall diagnosis result that the push data is not pushed to the designated push position according to the push logic indicated by the target push rule. Finally, the server 102 can output the recall diagnosis result of the push data.
[0066] Optionally, the server 102 may also modify the data push request initiated by the designated push location according to the recall diagnosis result of the push data, so that the modified data push request can obtain the corresponding push data for the designated push location. Optionally, the diagnosis platform and the push service platform may be run in the terminal device or in the server, and this is not limited. Optionally, the data processing method for the recall of the push data may also be performed by only Figure 1 The push data recall is executed by the terminal device 101 in the data processing system shown. The specific execution process can refer to the specific execution process of the server 102, which will not be repeated here.
[0067] In some other embodiments, the data processing method for push data recall may be run in a data processing system for push data recall, and the data processing system for push data recall may include a terminal device and a server. Figure 1The data processing system for push data recall shown is jointly completed by the terminal device 101 and the server 102, and the specific execution process is: the terminal device 101 can send a data push test request to the server 102; then, the server 102 will respond to the data push test request for the specified push position, and obtain the whiteboard data generated in the recall process of the push data from the push database to the specified push position through the push service platform. After that, the server 102 can obtain the target push rule that matches the specified push position from multiple push rules through the diagnosis platform. Then, the server 102 can obtain the data key field that matches the target push rule in the whiteboard data. If the server 102 determines that the semantics of the data key field does not match the push logic indicated by the target push rule, the server 102 can determine that the push data is not pushed to the specified push position, and generate a recall diagnosis result that the push data is not pushed to the specified push position according to the push logic indicated by the target push rule. Finally, the server 102 can send the recall diagnosis result of the push data to the terminal device 101, and the terminal device 101 outputs the recall diagnosis result of the push data.
[0068] Optionally, the terminal device 101 can also modify the data push request initiated by the designated push location according to the recall diagnosis result of the push data, so that the modified data push request can obtain the corresponding push data for the designated push location. Optionally, the diagnosis platform and the push service platform can run in the terminal device or in the server, which is not limited.
[0069] It should be noted that the embodiments of the present application can process data recalled from various push data and can be applied to various scenarios, including but not limited to cloud technology, AI (Artificial Intelligence), smart home, assisted driving and other scenarios. It can also be used to troubleshoot the reasons why push data cannot be recalled in various applications such as video applications, social applications, shopping applications, etc., without limitation.
[0070] Specifically, the technical solution of the embodiment of the present application can be applied to the smart home scene, such as the terminal device can be set as a smart refrigerator in the smart home scene, and the server can be a server that provides data processing services for the smart refrigerator to recall push data, and the push data can be recipes, beverages, supermarket discount information, etc. The display screen of the smart refrigerator may include multiple push positions. If the smart refrigerator detects that a certain push position does not display push data, the smart refrigerator can use the push position as a designated push position and generate a data push test request for the designated push position. Then, the smart refrigerator sends the data push test request to the server, and the server responds to the data push test request for the designated push position, and obtains the whiteboard data generated in the recall process of the push data from the push database to the designated push position through the push service platform. Then, the server can obtain the target push rule that matches the designated push position from multiple push rules through the diagnostic platform; thereafter, the server can obtain the data key field that matches the target push rule in the whiteboard data. If the server detects that the semantics of the data key field does not match the push logic indicated by the target push rule, the server can determine that the push data is not pushed to the designated push position, and generate a recall diagnosis result that the push data is not pushed to the designated push position according to the push logic indicated by the target push rule. Finally, the server can output the recall diagnosis results of the pushed data.
[0071] For another example, the technical solution of the embodiment of the present application is applied to troubleshooting the reasons why push data cannot be recalled in a video application. A diagnostic platform for push data related to the video application can be run in the terminal device, and the diagnostic platform can display multiple recommended positions in the video application, as well as one or more historical data push requests initiated by each recommended position. Then, the terminal device can respond to the R&D personnel's selection operation on multiple recommended positions in the diagnostic platform to obtain the designated recommended position; and the terminal device can also respond to the R&D personnel's selection operation on one or more historical data push requests initiated by the designated recommended position in the diagnostic platform to obtain the target data push request. Afterwards, the terminal device can send the designated push position and the target data push request to the server, so that the server generates a data push test request for the designated push position based on the target data push request.
[0072] Afterwards, the server can respond to the data push test request for the designated push position, and obtain the whiteboard data generated during the recall process of the push data from the push database to the designated push position through the push service platform. Then, the server can obtain the target push rule that matches the designated push position from multiple push rules through the diagnostic platform; then, the server can obtain the data key field that matches the target push rule in the whiteboard data. If the server detects that the semantics of the data key field does not match the push logic indicated by the target push rule, the server can determine that the push data is not pushed to the designated push position, and generate a recall diagnosis result that the push data is not pushed to the designated push position according to the push logic indicated by the target push rule. Finally, the server can send the recall diagnosis result of the push data to the terminal device, so that the terminal device can display the recall diagnosis result of the push data through the diagnostic platform.
[0073] It should be noted that in the specific implementation of this application, if the recommended data, whiteboard data and other related data or information are related to the object, when the embodiment of this application is applied to a specific product or technology, it is necessary to obtain the permission or consent of the object, and the collection, use and processing of the relevant data or information need to comply with the relevant laws, regulations and standards of the relevant countries and regions.
[0074] The following is a detailed description of various implementation details of the technical solution of the embodiment of the present application:
[0075] like Figure 2 As shown, Figure 2 is a flow chart of a data processing method for push data recall shown in an embodiment of the present application, which can be applied to Figure 1 The data processing system for push data recall shown in the figure, the method can be executed by the terminal device or the server, or can be executed by the terminal device and the server together. In the embodiment of the present application, the method is executed by the server as an example for explanation, wherein the data processing method for push data recall may include S201 to S205, which are described in detail as follows:
[0076] S201, responding to a data push test request for a designated push location, obtaining whiteboard data generated during a recall process of push data from a push database to the designated push location through a push service platform.
[0077] In the embodiment of the present application, the push position refers to the position in the application interface of the application software where the push data is displayed. The designated push position refers to a specific push position in the application interface of the application software.
[0078] In addition, a data push test request refers to a data push request that has been modified to a debug state, that is, the data push test request contains debug = true. Specifically, a data push test request can be generated by making certain modifications to a historical data push request initiated by a specified recommendation position. At the same time, the number of pushed data can be one or more. Accordingly, there is a corresponding relationship between the pushed data and the whiteboard data, so the number of whiteboard data can also be one or more.
[0079] In addition, the push service platform is used to recall the push data, that is, to determine the push data that is finally output at the push position from the push data in the push database. The whiteboard data includes the processing data of the push data during the recall process.
[0080] In one embodiment, the designated push position may be determined by: the server displays multiple push positions; and in response to a selection operation on the multiple push positions, obtains the selected designated push position.
[0081] Optionally, the designated push position may be determined in the following manner: if the server detects that any push position in the application interface does not display push data, then the push position is used as the designated push position.
[0082] Optionally, personalized recommendations are sometimes made based on different objects. Therefore, if the objects logging into the application software are different, the push data displayed in the same recommendation position in the application software will also be different, resulting in different reasons for not being able to recall the push data when the objects are different. Therefore, the method for determining the designated push position can also be: the server can display a push configuration interface including object configuration options; then, the server responds to the editing operation of the object configuration options and determines the configured object; thereafter, the server can obtain multiple recommendation positions that the configured object has browsed during the use of the application software, and display the obtained multiple recommendation positions; finally, the server can respond to the selection operation of the obtained multiple recommendation positions and obtain the selected designated recommendation position. Optionally, the designated push position can also be determined by other methods, which are not limited to this.
[0083] In one embodiment, the push service platform may be deployed in other servers. Then the whiteboard data may be obtained by: the server sends a data push test request to the push service platform, so that the push service platform responds to the data push test request, and in the process of calling each module to process the push data, obtains the processing data of each module, wherein the processing data includes processing process data and processing result data; the push service platform sends the obtained processing data as whiteboard data to the server.
[0084] Specifically, since the push service platform includes modules such as directional matching, mixed / rough sorting, fine sorting, and push data filling, and the whiteboard data includes the processing data of the push data during the recall process, the whiteboard data can specifically include which directions the push data does not match, which directions it matches, which push data queues it enters, which push data queues it is filtered by, and the reasons for filtering, etc.
[0085] In one embodiment, a push service platform may be running in the server itself, and the whiteboard data may be obtained in the following manner: the server responds to a data push test request for a specified push position through the push service platform, and obtains a data reply packet of the data push test request; wherein the data reply packet contains the whiteboard data corresponding to the push data. After receiving the data push test request, the push service platform processes the push data according to the arrangement order of each module, and records the processing information of each module during the processing process, so as to generate a data reply packet containing the whiteboard data.
[0086] It should be noted that, since some push data may be filtered in one of the modules such as directional matching, mixed / coarse sorting, fine sorting and push data filling, the processed data obtained by the module arranged after the aforementioned module in the push service platform will not be obtained. Therefore, the whiteboard data of these push data can only include the processed data of the aforementioned module and the processed data of each module arranged before the aforementioned module in the push service platform.
[0087] S202: Acquire a target push rule matching a designated push position from multiple push rules through a diagnosis platform.
[0088] In the embodiment of the present application, different push rules indicate different push logics. Each push rule can be obtained by sorting and analyzing the processing logic of each module such as directional matching, mixed / coarse sorting, fine sorting, and push data filling, or by summarizing the analysis experience of the debugger on the whiteboard data, which is not limited to this.
[0089] At the same time, the diagnosis platform may store multiple push rules, and the diagnosis platform may be further used to analyze the recall diagnosis results of the push data through multiple push rules. The diagnosis platform may be deployed in the server in the embodiment of the present application, or in other servers, without limitation.
[0090] In addition, the specific method of obtaining the target push rule matching the designated push position from multiple push rules through the diagnostic platform can be: obtaining the push range information of the designated push position through the diagnostic platform; obtaining the candidate push rule and the adaptation range information of the candidate push rule from multiple push rules; if the adaptation range information of the candidate push rule matches the push range information, the candidate push rule is determined as the target push rule. It should be noted that the adaptation range information of different push rules is not exactly the same.
[0091] Among them, the adaptation scope information of the candidate push rules includes the scenarios or conditions in which the candidate push rules can be used. Each push rule carries corresponding adaptation scope information. Optionally, the adaptation scope information of some push rules is applicable to all scenarios and conditions, then such push rules will definitely match the specified push position. Optionally, the push scope information of the specified push position may be carried by the data push test request after the specified push position initiates the data push test request, so the diagnostic platform can directly obtain the push scope information of the specified push position.
[0092] In addition, the specific method of obtaining candidate push rules from multiple push rules through the diagnostic platform can be to randomly select a push rule from multiple push rules as a candidate push rule through the diagnostic platform. Optionally, multiple push rules can be arranged in a certain order, then the specific method of obtaining candidate push rules through the diagnostic platform can also be: select a push rule according to the arrangement order of multiple push rules through the diagnostic platform, and use the selected push rule as the candidate push rule. Optionally, candidate push rules can also be obtained from multiple push rules through other methods, which are not limited to this.
[0093] At the same time, the push range information may include at least one of the following: associated push data of the specified push position, push position information of the specified push position, application identification information of the application to which the specified push position belongs, and environment identification information of the initiation environment of the data push request initiated by the specified push position.
[0094] In one embodiment, specifically, the associated push data of the designated push position may include one or more of the following: push data that can be displayed by the preset designated push position, push data that cannot be displayed by the preset designated push position, push data that can be displayed by the designated push position within a first preset time, push data that cannot be displayed by the designated push position within a second preset time, etc. Among them, the first preset time and the second preset time can be set according to factors such as the delivery demand and delivery price of the delivery object of the push data, and there is no limitation on this.
[0095] Since there may be a situation where the designated push position is set to display only certain push data, and the adaptation scope information of some push rules may include the push data applicable to the corresponding push rules, if the associated push data of the designated push position does not belong to the push data applicable to the candidate push rule, it can be determined that the adaptation scope information of the candidate push rule does not match the push scope information; if the associated push data of the designated push position belongs to the push data applicable to the candidate push rule, it can be determined that the adaptation scope information of the candidate push rule matches the push scope information.
[0096] In one embodiment, the push position information of the designated push position may include one or more of various information such as push position identification information of the designated push position, interface identification information of the display interface of the designated push position included in the application software, location identification information of the designated push position in the corresponding interface, and proxy processing information carried in the data push request initiated by the designated push position, without limitation.
[0097] Since different push logics may be designed for push bits at different positions, the adaptation range information of some push rules may include the position information of the push bits to which the corresponding push rules apply. Then, if the position indicated by the push bit information of the designated push bit is different from the position information to which the candidate push rule applies, it can be determined that the adaptation range information of the candidate push rule does not match the push range information; if the position indicated by the push bit information of the designated push bit is the same as the position information to which the candidate push rule applies, it can be determined that the adaptation range information of the candidate push rule matches the push range information.
[0098] In one embodiment, the application identification information of the application to which the specified push position belongs may include one or more of the following information: a unique identifier indicating the application to which the specified push position belongs, an application type of the application to which the specified push position belongs, etc., which is not limited thereto.
[0099] Since different push logics may be designed for applications of different application types or for different applications, the adaptation scope information of some push rules may include the application or application type to which the corresponding push rule applies, etc. Then, if the application or application type indicated by the application identification information of the specified push bit is different from the application or application type to which the candidate push rule applies, it can be determined that the adaptation scope information of the candidate push rule does not match the push scope information; if the application or application type indicated by the application identification information of the specified push bit is the same as the application or application type to which the candidate push rule applies, it can be determined that the adaptation scope information of the candidate push rule matches the push scope information.
[0100] In one embodiment, the environment identification information is used to indicate the initiation environment of the data push request initiated by the designated push location.
[0101] The research and development and iterative updates of application software are highly dependent on application software built in multiple environments, such as test environments (environments used to test the functions of application software), online environments (application software actually used by the subject), sandbox environments (environments that are highly similar to online environments), etc. The same push location of application software in different environments may have different push logics, so the adaptation scope information of certain push rules may include the environment to which the corresponding push rules apply. Then, if the initiating environment indicated by the environment identification information is different from the environment to which the candidate push rule applies, it can be determined that the adaptation scope information of the candidate push rule does not match the push scope information; if the initiating environment indicated by the environment identification information is the same as the environment to which the candidate push rule applies, it can be determined that the adaptation scope information of the candidate push rule matches the push scope information.
[0102] In a possible implementation, since the aforementioned push rules can be obtained by sorting and analyzing the processing logic of each module such as directional matching, mixed / rough sorting, fine sorting, and push data filling, the adaptation range information of some push rules can further include one or more of the information such as the orientation, the rough sorting method, and the filling method applicable to the corresponding push rules. The whiteboard data includes the processing data of each module, so the push range information can further include the whiteboard data.
[0103] For example, if the orientation contained in the whiteboard data is different from the orientation applicable to the candidate push rule, it can be determined that the adaptation range information of the candidate push rule does not match the push range information; if the orientation contained in the whiteboard data is the same as the orientation applicable to the candidate push rule, it can be determined that the adaptation range information of the candidate push rule matches the push range information.
[0104] S203: Acquire key data fields in the whiteboard data that match the target push rule.
[0105] In the embodiment of the present application, since the whiteboard data includes the processing data of each module in the recall process, and the processing data is mainly fields, the specific method of obtaining the key data fields in the whiteboard data that match the target push rule can be: obtaining the text similarity between each field in the whiteboard data and the target push rule, and determining the field whose text similarity is greater than the preset similarity threshold as the key data field.
[0106] Among them, the preset similarity threshold can be set manually, or it can be set by the server or terminal device in the data processing system of the above-mentioned push data recall, which is not limited to this. Optionally, the key data field can also be obtained by other means, which is not limited to this. In addition, since the field is a text, the target push rule is also a text, and the method of obtaining the text similarity between the two texts is a technical means commonly used by those skilled in the art, so it will not be repeated here.
[0107] S204. If the semantics of the key data field does not match the push logic indicated by the target push rule, it is determined that the push data is not pushed to the designated push location, and a recall diagnosis result that the push data is not pushed to the designated push location is generated according to the push logic indicated by the target push rule.
[0108] In an embodiment of the present application, the recall diagnosis result is used to prompt that the push data is not pushed to the specified push position and the push logic is not satisfied, which is also equivalent to prompting the reason why the push data cannot be recalled. Specifically, the recall diagnosis result can be a text that describes the push logic that the push data does not satisfy. Optionally, a correspondence between the result identifier and the reason why the recall cannot be made can also be established in advance, so the recall diagnosis result can be the result identifier corresponding to the reason why the recall cannot be made. Among them, the result identifier can be identification information such as characters, numbers, images, etc. that can uniquely identify the reason why the recall cannot be made, and there is no limitation on this.
[0109] Since the semantics of the key data fields do not match the push logic indicated by the target push rule, it means that the push data is filtered out in the processing logic that is similar or the same as the push logic indicated by the target push rule. Therefore, the push logic indicated by the target push rule is the push logic that is not satisfied by the push data not being pushed to the designated push position. Then, the specific method of generating the recall diagnosis result of the push data can be to directly analyze and process the push logic indicated by the target push rule to generate the recall diagnosis result of the push data.
[0110] In one embodiment, whether the semantics of the data key field matches the push logic indicated by the target push rule may refer to whether the semantics of the data key field is similar to or identical to the semantics of the target push rule.
[0111] Optionally, the specific method for determining whether the semantics of the data key field matches the push logic indicated by the target push rule may be: splicing the data key field with the target push rule to obtain a spliced text; performing semantic correlation recognition processing on the spliced text to obtain the semantic correlation between the data key field and the target push rule; if the semantic correlation is less than or equal to a preset correlation threshold, it is determined that the semantics of the data key field does not match the push logic indicated by the target push rule.
[0112] Optionally, if the semantic relevance is greater than a preset relevance threshold, it is determined that the semantics of the key data field matches the push logic indicated by the target push rule.
[0113] Among them, the preset relevance threshold can be set manually, or it can be set by the server or terminal device in the data processing system of the above-mentioned push data recall, and there is no limitation on this. Furthermore, semantic relevance recognition processing can be performed through the trained relevance recognition model. Specifically, the trained relevance recognition model can be obtained by training pre-trained language models such as BERT model (Bidirectional Encoder Representations from Transformer), XLNet (autoregressive and autoencoder model), LayoutLM (Pre-training of Text and Layout for Document Image Understanding). Since the specific method of the relevance recognition model is a technical means commonly used by those skilled in the art, it will not be elaborated here.
[0114] For example, the target push rule can be to determine whether the delivery time of the push data R is between 10 and 11 o'clock; after obtaining the data key field Q in the whiteboard data of the push data R that matches the target push rule, if the semantics of the data key field Q indicates that the delivery time of the push data R is 12:10, then it means that the semantics of the data key field Q does not match the push logic indicated by the target push rule that the delivery time is between 10 and 11 o'clock. Therefore, based on the push logic indicated by the target push rule, it can be diagnosed that the push logic that the push data R does not meet is the delivery time between 10 and 11 o'clock, thereby generating a recall diagnosis result for the push data R. Optionally, it can also be analyzed based on the inverse logic of the push logic indicated by the target push rule that the reason why the push data R cannot be recalled is that the delivery time is not between 10 and 11 o'clock, thereby generating a recall diagnosis result for the push data R.
[0115] Furthermore, since the data key fields in the whiteboard data specifically describe where the pushed data is filtered during the recall process, the specific method of generating the recall diagnosis results of the pushed data according to the target push rules can also be: generating the recall diagnosis results of the pushed data according to the semantics of the data key fields and the push logic indicated by the target push rules.
[0116] S205: Output the recall diagnosis result of the pushed data.
[0117] In an embodiment of the present application, the specific method of outputting the recall diagnosis result of the pushed data may be: displaying the recall diagnosis result of the pushed data. Optionally, the recall diagnosis result of the pushed data may be outputted via SMS, email, etc. Optionally, the recall diagnosis result of the pushed data may be outputted via other methods, which are not limited.
[0118] Optionally, a correspondence between recall diagnosis results and solutions can be established based on the debugging personnel's experience in manually troubleshooting the problem of being unable to recall pushed data; then, on the basis of outputting the recall diagnosis results of the pushed data, the server can also search for solutions corresponding to the recall diagnosis results; and then, when outputting the recall diagnosis results of the pushed data, the server can also output the solutions corresponding to the recall diagnosis results together.
[0119] Optionally, the solution may include a push request modification method. After the server finds the push request modification method corresponding to the recall diagnosis result, it can modify the data push request initiated by the designated push position so that the modified data push request can obtain the corresponding push data for the designated push position.
[0120] In actual applications, the threshold for analyzing whiteboard data is very high. On the one hand, there is a lot of data to be processed. The average whiteboard data has about 120,000 lines of data, and debuggers need to check and analyze them one by one. On the other hand, most of the whiteboard data is highly professional data, and only people with specific development and debugging experience can analyze the whiteboard data.
[0121] In an embodiment of the present application, by judging whether the semantics of the key data fields in the whiteboard data match the push logic indicated by the target push rule, when the semantics of the key data fields do not match the push logic indicated by the target push rule, the recall diagnosis result of the push data can be directly generated according to the push logic indicated by the target push rule. It can be seen that the embodiment of the present application can autonomously find out the reasons why the push data cannot be recalled, avoiding the scenario where the whiteboard data needs to be manually analyzed to troubleshoot the problem, greatly improving the efficiency of problem troubleshooting, and reducing the time, labor and other troubleshooting costs. At the same time, the embodiment of the present application will screen a plurality of push rules to a certain extent, and only the push rules that match the specified push position will be used as the target push rules for the next step of judgment; avoiding the situation where multiple fields in the whiteboard data need to be logically compared one by one with multiple push rules. Therefore, the embodiment of the present application can further improve the troubleshooting efficiency by accurately screening out the target push rules suitable for the specified push position.
[0122] In addition, since the version update test of the application software depends on the recall of the pushed data, only when the pushed data can some interactive logic about the pushed data in the application software running on the terminal device be verified. The embodiment of the present application can greatly improve the efficiency of troubleshooting the problem of being unable to recall the pushed data, thereby reducing the situation of version update test blockage caused by the inability to recall the pushed data, and further helping to reduce the risk of application software demand delay caused by version test blockage.
[0123] In one embodiment of the present application, another data processing method for push data recall is provided, and the data processing method for push data recall can be applied to Figure 1 The data processing system for pushing data recall shown in the figure can be executed by a terminal device or a server, or can be executed by a terminal device and a server together. In the embodiment of the present application, the method is executed by a server as an example for explanation. Figure 3 FIG. 1 is a flow chart showing another method for processing push data recall data. The method for processing push data recall data is Figure 2 This is an extension of the method shown in .
[0124] Among them, S301 to S307 are described in detail as follows:
[0125] S301, responding to a data push test request for a designated push location, obtaining whiteboard data generated during a recall process of push data from a push database to the designated push location through a push service platform.
[0126] In the embodiment of the present application, the specific implementation of step S301 can refer to the specific implementation of step S201 in the above embodiment, which will not be repeated here.
[0127] S302: Obtain push range information of a specified push location through a diagnostic platform.
[0128] In the embodiment of the present application, referring to the description of the push range information in step S202, the push range information may include at least one of the following: the associated push data of the designated push position, the push position information of the designated push position, the application identification information of the application to which the designated push position belongs, and the environment identification information of the initiation environment of the data push request initiated by the designated push position. Optionally, the push range information may further include whiteboard data. The specific description of the associated push data, push position information, application identification information, and environment identification information can be found in the specific implementation manner in step S202, which will not be repeated here.
[0129] S303: Select push rules in sequence according to the arrangement order of the multiple push rules, and match the adaptation scope information of the selected push rules with the push scope information until the adaptation scope information of the selected push rules matches the push scope information.
[0130] In the embodiment of the present application, multiple push rules can be arranged in a preset order. Among them, since the matching result of the push logic indicated by a part of the push rules and the corresponding field in the whiteboard data may affect the matching result of the push logic indicated by another part of the push rules and the corresponding field in the whiteboard data; wherein the matching result is used to indicate whether the semantics of the field in the whiteboard data matches the push logic indicated by the corresponding push rule.
[0131] At the same time, since the recall process of push data filters the push data in the order of rough sorting, fine sorting, etc., if the push data is filtered during rough sorting, then there is no need to match the push rules for fine sorting, so the push rules for rough sorting can be placed before the push rules for fine sorting. Therefore, the preset order can be determined according to the debugging experience of the debugging personnel, and then multiple push rules can be arranged according to the preset order.
[0132] Specifically, the first push rule among multiple push rules can first be used as a candidate push rule, and the first push rule can be used as the adaptation scope information of the candidate push rule; if the adaptation scope information of the candidate push rule matches the push scope information, the candidate push rule is determined as the target push rule; if the adaptation scope information of the candidate push rule does not match the push scope information, the next push rule of the candidate push rule is used as a new candidate push rule, and the adaptation scope information of the next push rule is used as the adaptation scope information of the new candidate push rule, until the adaptation scope information of the new candidate push rule matches the push scope information, the new candidate push rule is used as the target push rule.
[0133] S304: Use the push rule whose adaptation scope information matches the push scope information as the target push rule.
[0134] In the embodiment of the present application, the specific implementation of step S304 can refer to the specific implementation of step S202 in the above embodiment, which will not be repeated here.
[0135] S305: Acquire key data fields in the whiteboard data that match the target push rule.
[0136] In the embodiment of the present application, the specific implementation of step S305 can refer to the specific implementation of step S203 in the above embodiment, which will not be repeated here.
[0137] S306. If the semantics of the key data field does not match the push logic indicated by the target push rule, it is determined that the pushed data is not pushed to the designated push location, and a recall diagnosis result that the pushed data is not pushed to the designated push location is generated according to the push logic indicated by the target push rule.
[0138] In the embodiment of the present application, the specific implementation of step S306 can refer to the specific implementation of step S204 in the above embodiment, which will not be repeated here.
[0139] S307: Output the recall diagnosis result of the pushed data.
[0140] In the embodiment of the present application, the specific implementation of step S307 can refer to the specific implementation of step S205 in the above embodiment, which will not be repeated here.
[0141] Optionally, if the data push test request carries proxy processing information, the recall diagnosis result of the pushed data is sent to the proxy processing platform, so that the proxy processing platform obtains a push request modification method that matches the recall diagnosis result of the pushed data, and modifies the data push request initiated by the designated push position according to the push request modification method.
[0142] Among them, the data push request modified by the proxy processing platform can enable the specified push position to display the push data. For example, if the recall diagnosis result of the push data indicates that the reason why the push data cannot be recalled is that it is filtered in direction Y, then the push request modification method obtained by the proxy processing platform that matches the recall diagnosis result of the push data can be to modify the data push request so that the push data can skip direction Y.
[0143] It can be seen that the proxy processing platform can further reduce the work of debugging personnel, realize the full automation of the process of troubleshooting the reasons why the pushed data cannot be recalled, and solve the problem of not being able to recall the pushed data, which is conducive to further reducing time, labor and other costs.
[0144] In a possible implementation, if the semantics of the key data field matches the push logic indicated by the target push rule, the push rule that is arranged after the target push rule and matches the designated push position can be used as the new target push rule; then, the new key data field in the whiteboard data that matches the new target push rule is obtained. Finally, when the semantics of the new key data field does not match the push logic indicated by the new target push rule, it is determined that the push data is not pushed to the designated push position, and a recall diagnosis result of the push data is generated according to the push logic indicated by the new target push rule.
[0145] Optionally, since the matching result between the push logic indicated by a part of the push rules and the whiteboard data mentioned in step S302 may affect the matching result between the push logic indicated by another part of the push rules and the corresponding fields in the whiteboard data, the specific method for judging whether the new data key field conforms to the push logic indicated by the new target push rule can also be: judging whether the new data key field matches the push logic indicated by the new target push rule based on the matching result between the target push rule before the new target push rule and the corresponding data key field in the whiteboard data.
[0146] For example, multiple push rules may include proxy processing rules and stability rules. The push logic indicated by the proxy processing rule is: detect whether the data push test request initiated by the specified push position carries the proxy processing information, and the adaptation scope information of the proxy processing rule does not limit the applicable scenarios and conditions of the proxy processing rule; the push logic indicated by the stability rule is: detect whether the initiating environment for initiating the data push test request is available, and the adaptation scope information of the stability rule is the preset environment, wherein the preset environment can be one or more of the test environment, online environment, and sandbox environment mentioned in step S202.
[0147] If the data push test request initiated by the designated push position carries the proxy processing information, the proxy processing platform may edit the data push test request, resulting in the final initiation environment of the data push test request being the initiation environment of the proxy processing platform, while the initiation environment previously obtained is the initiation environment of the data push test request initiated by the designated push position. Therefore, if the proxy processing rule detects that the data push test request initiated by the designated push position carries the proxy processing information, the server may need to re-acquire the initiation environment of the proxy processing platform to judge the subsequent stability rules.
[0148] For specific implementation, please refer to the attached Figure 4 , shows a schematic diagram of the architecture of a rule engine module. Figure 4 As shown, the rule engine module includes an ordered rule pool 401 and a scheduler 402. The ordered rule pool 401 contains multiple push rules, such as Figure 4 As shown, the ordered rule pool 401 includes multiple push rules such as proxy processing rules, stability rules, push rules for push data A, and push rules for targeted M. Among them, the push logic of the push rule for push data A may include whether the delivery time of push data A is within the specified delivery time of push data A, whether push data A is valid, etc. The push logic of the push rule for targeted M may be: whether the push data is filtered when targeted M.
[0149] like Figure 4As shown in the push rules for push data A and the push rules for directed M, before writing each push rule into the ordered rule pool 401, it is also necessary to pre-register the priority of each push rule in order to determine the order of each push rule in the ordered rule pool 401. It should be noted that the priority of each push rule can be registered and set by the debugger through debugging experience, or can be set by the terminal device or server in the data processing system for the above-mentioned push data recall, and this is not limited.
[0150] After the server obtains the whiteboard data generated in the recall process of the push data B from the push database to the designated push position, the server can obtain the candidate push rules from the ordered rule pool 401 through the scheduler 402, where Figure 4 As shown, the candidate push rule obtained for the first time is the proxy processing rule.
[0151] Then, the scheduler 402 will further execute step 403 to determine whether the adaptation range information of the candidate push rule matches the push range information of the specified push position. If it does not match, the scheduler 402 will re-acquire the next push rule of the candidate push rule from the ordered rule pool 401 as a new candidate push rule; if it matches, the scheduler 402 will input the candidate push rule as the target push rule and the whiteboard data into the rule matching processing unit 404, and the rule matching processing unit 404 will determine the data key field in the whiteboard data that matches the target push rule, and match and compare the push logic indicated by the target push rule with the semantics of the data key field to obtain a matching result; wherein, the matching result is used to indicate whether the semantics of the data key field matches the push logic indicated by the target push rule.
[0152] Afterwards, the scheduler 402 will execute step 405, that is, determine whether to end the scheduling according to the matching result output by the rule matching processing unit 404. If the matching result indicates that the semantics of the key data field matches the push logic indicated by the candidate push rule as the target push rule, it means that the scheduling is not ended, and the scheduler 402 will re-acquire the next push rule of the candidate push rule from the ordered rule pool 401 as a new candidate push rule, and execute all the above steps. If the matching result indicates that the semantics of the key data field does not match the push logic indicated by the candidate push rule as the target push rule, it means that the scheduling is ended, and the scheduler 402 can execute step 406, that is, generate a recall diagnosis result according to the push logic indicated by the candidate push rule.
[0153] In actual application, please refer to the attached Figure 5A, showing an interface diagram of a push configuration interface. The push configuration interface 501 includes an object ID input box 502 (i.e., object configuration options). The object ID entered by the debugger in the object ID input box 502 is 111225632; then, the request selection interface 503 will be displayed, and the request selection interface 503 contains historical data push requests initiated by multiple recommended positions browsed by object 111225632. Among them, the recommended position 8040486525039375 is the recommended position in the function 001 interface of application A, and object 111225632 browsed the recommended position 8040486525039375 at 2023-01-10-17:48:30. In addition, the other recommended positions 9091815123853236 and 1041913173657237 in the request selection interface 503 are the same, and they will not be repeated here.
[0154] Optional, such as Figure 5A As shown, the push configuration interface 501 may also include an environment information option for the debugger to select the launching environment for launching the data push test request. Figure 5A As shown, the push configuration interface 501 may also include an agent processing option for the debugger to select whether to allow the data push test request to carry the agent processing information. Figure 5A As shown, the push configuration interface 501 may also include a device address option for the debugger to select a terminal device for initiating a data push test request. Optionally, the push configuration interface 501 may also include other configuration options for information such as objects, push positions, and initiation environments, which are not limited thereto.
[0155] After the debugger selects a data push request initiated by a certain push position (i.e., a designated push position) in the request selection interface 503, the interface will return to the push configuration interface 501. After that, the debugger can click the "one-key diagnosis" button 504, at which time the server will respond to the "one-key diagnosis" selection operation, generate a data push test request according to the data push request selected by the debugger, and respond to the data push test request to obtain the whiteboard data generated during the recall process of the push data from the push database to the designated push position. After that, the server will call the aforementioned rule engine module to process the whiteboard data corresponding to the push data to obtain the recall diagnosis result of the push data.
[0156] Finally, see the attached Figure 5B, showing a schematic diagram of a display interface for recalling diagnostic results. As shown in display interface 505, the recall diagnostic result includes the reason why the pushed data cannot be recalled, that is, the push logic that the pushed data is not pushed to the specified push position is not satisfied, that is, the directional mismatch, specifically the directional M mismatch; at the same time, display interface 505 also shows a solution, that is, you can turn on the nomatch switch (the nomatch switch is a no-match switch, turning on the nomatch switch is to add nomatch=true information in the data push request) to skip the directional. Among them, display interface 505 also displays some detailed data about directional M, namely data 506 to 508, so that the debugging personnel can perform precise processing.
[0157] Optionally, since the number of pushed data mentioned in step S201 may be one or more, please refer to the attached Fig. 6A , showing a schematic diagram of a display interface for recall diagnosis results of multiple pushed data. As shown in the diagnostic funnel information interface 601, the recall diagnosis results of multiple pushed data can simultaneously display the environment information of the specified push position initiating the data push test request, such as the environment is a test environment, and the IP address (Internet Protocol Address) of the test environment is "7.11.26.220:0330".
[0158] Optionally, the diagnostic funnel information interface 601 may also display object attributes, traffic attributes, and strong pull attributes. Among them, the object attributes may include one or more of the object name, object identifier, and object identifier. The traffic attributes may include the application type of the application to which the specified push position belongs, the push service type to which the specified push position belongs, etc.; for example, the traffic attributes may be video, news, education, etc., which are not limited to this. The strong pull attributes may include the associated push data of the specified push position.
[0159] Optionally, as shown in the request funnel part of the diagnostic funnel information interface 601, basic information about the specified push position 6001849590817219, such as supported material specifications, supported product types, supported bid types, and push position status, can also be displayed.
[0160] Among them, the supported material specifications may include the data type and data specifications of the push data, such as the data type may be an image, a video, etc., and the data size may be the size of the image, the specifications of the video, etc.; 123 in the diagnostic funnel information interface 601 may indicate that the data type of the push data is an image, and 124 may indicate that the data type of the push data is a video, which means that the designated push position can display both images and videos. The supported product type refers to the type of external link that can be jumped after clicking the push data of the designated push position. For example, 12 in the diagnostic funnel information interface 601 may specify that the external link product type that the push position supports jumping to is a mini-program in a certain session application. The supported bid type refers to the price threshold required to display the push data in the designated push position. Different bid types indicate different price thresholds. The push position status refers to whether the push position is valid or frozen, where 1 can be set to indicate that the push position is valid, and 0 can indicate that the push position is frozen.
[0161] In addition, after receiving the data push test request for the designated push position, the push system will obtain multiple push data from the push database, and then the multiple push data will go through the recall, rough sorting, fine sorting and winning stages, and only the finally winning push data will be displayed in the designated push position. Therefore, as shown in the request funnel part of the diagnostic funnel information interface 601, the recall process of the push data can be presented in the form of a push data recall queue, and the push data recall queue can be divided into the recall, rough sorting, fine sorting and winning stages.
[0162] As shown in the diagnostic funnel information interface 601, the server responds to the data push test request for the push position through the push system, and obtains 45 push data from the push database. Then, these 45 push data enter the recall stage. After selection and retrieval, the recall stage does not filter the push data; therefore, the 45 push data enter the rough sorting stage.
[0163] Among them, there are two filtering stages in the rough sorting stage. As shown in the diagnostic funnel information interface 601, 10 push data are filtered out in the first filtering stage of the rough sorting stage, and no push data are filtered out in the second filtering stage of the rough sorting stage. Afterwards, the rough sorting stage outputs the remaining 35 push data to the fine sorting stage, and 32 push data are filtered out in the fine sorting stage. Finally, the remaining 3 push data in the fine sorting stage will be sorted, and only the push data ranked first will be output to the winning stage.
[0164] Through the push data recall queue in the diagnostic funnel information interface 601, the filtering status of the push data can be intuitively and clearly seen, so that the debugging personnel can have a macroscopic understanding of the recall status of the push data of the designated push position.
[0165] For further information, please see the attached Figure 6B , showing an interface diagram of filtering reasons in the rough sorting stage. After the debugger clicks on the relevant position of the rough sorting stage in the diagnostic funnel information interface 601, the interface can jump to interface 602, wherein interface 602 displays the ID of the pushed data filtered in the rough sorting stage, and the filter code of each pushed data. Different filter codes are used to indicate different reasons for failure to recall. Optionally, after the debugger clicks on any push data ID, the data content of the corresponding push data can be further displayed. Optionally, after the debugger clicks on any filter code, the reason for failure to recall the push data indicated by the corresponding filter code can be further displayed.
[0166] For further information, please see the attached Figure 6C , showing an interface diagram of the reasons for filtering in the fine sorting stage. After the debugging personnel clicks on the relevant position of the fine sorting stage in the diagnostic funnel information interface 601, the interface can jump to interface 603, wherein interface 603 displays the ID of the push data filtered in the fine sorting stage, the delivery object of each push data, the commodity type of each push data, and the filter code of each push data. Among them, the delivery object refers to the object that spends money to deliver push data in the push position. Optionally, after the debugging personnel clicks on any push data ID, any delivery object, any commodity type or any filter code, the data content of the corresponding push data, the object attributes of the corresponding delivery object, the type of external link indicated by the corresponding commodity type, or the reason why the push data cannot be recalled indicated by the corresponding filter code can be further displayed.
[0167] In an embodiment of the present application, by determining whether the semantics of the key data fields in the whiteboard data match the push logic indicated by the target push rule, it is possible to autonomously troubleshoot the reasons why the push data cannot be recalled, avoiding the need to manually analyze the whiteboard data to troubleshoot the problem, greatly improving the troubleshooting efficiency and reducing the troubleshooting cost. At the same time, the embodiment of the present application will perform certain screening on multiple push rules, and only the target push rule will proceed to the next step of judgment. Therefore, the embodiment of the present application can further improve the troubleshooting efficiency by accurately screening out the target push rules suitable for the specified push position.
[0168] In addition, since the matching results of the push logic indicated by one part of the push rules and the corresponding fields in the whiteboard data may affect the matching results of the push logic indicated by another part of the push rules and the corresponding fields in the whiteboard data, the embodiment of the present application selects the target push rules adapted to the push range information in a preset order, which makes the investigation more accurate and helps to improve the accuracy of the recall diagnosis results.
[0169] In one embodiment of the present application, another data processing method for push data recall is provided, and the data processing method for push data recall can be applied to Figure 1 The data processing system for pushing data recall shown in the figure can be executed by a terminal device or a server, or can be executed by a terminal device and a server together. In the embodiment of the present application, the method is executed by a server as an example for explanation. Figure 7 As shown, a flow chart of another method for processing push data recall is shown. Figure 2 and Figure 3 This is an extension of the method shown in .
[0170] Among them, S701 to S708 are described in detail as follows:
[0171] S701: Obtain object identification information of a specified object and push position identification information of a specified push position.
[0172] In an embodiment of the present application, the specific method of obtaining the object identification information of a specified object and the push position identification information of a specified push position may be: displaying a push configuration interface containing object configuration options; then, in response to an editing operation on the object configuration options, obtaining the object identification information of the configured specified object; thereafter, obtaining multiple recommendation positions browsed by the specified object during the use of the application software, and displaying the recommendation position identification information of the obtained multiple recommendation positions; finally, in response to a selection operation on the obtained multiple recommendation position identification information, obtaining the recommendation position identification information of the selected specified recommendation position.
[0173] In one embodiment, the objects stored in the object request database may be colored objects, that is, objects added to the whitelist of the application software by the debugger. In a specific implementation, the object request database may be an Eagle Eye platform (an object data perspective system that can query data push requests of colored objects).
[0174] S702: Search, from an object request database, for a historical data push request initiated by a designated object through a designated push position according to the object identification information and the push position identification information.
[0175] In the embodiment of the present application, the object request database is used to store historical data push requests initiated by multiple objects through multiple push positions. The designated object, the push position and the historical data push request are correspondingly stored in the object database, so the historical data push request initiated by the designated object through the designated push position can be found from the object request database according to the acquired object identification information and push position identification information.
[0176] In one embodiment, it is possible that the designated object obtained by the debugger editing the object configuration options in the push configuration interface is not a dyed object, and the object request database only stores historical data push requests corresponding to the dyed object. In this case, the historical data push requests for the designated object cannot be found in the object request database.
[0177] Therefore, optionally, if the historical data push request initiated by the specified object through the specified push position is not found in the object request database, a data push request matching the push position identification information can be obtained from the online request database used to store historical data push requests initiated through multiple push positions; wherein the obtained data push request is used to obtain push data for the specified push position; finally, based on the obtained historical data push request, a data push test request is generated. In a specific implementation, the online request database can be a data warehouse, that is, an online request sampling system, which can query the real data push request of the online object according to the push position.
[0178] S703: Generate a data push test request based on the found historical data push request.
[0179] In the embodiment of the present application, since different data push requests may be written using different request protocols, and the debug field positions in different request protocols are different, the process of the server automatically modifying the data push request to a debug state data push test request will be very complicated and difficult to adapt to different request protocols.
[0180] Therefore, based on the historical data push requests found, the specific method of generating a data push test request can be: converting the data format of the historical data push requests found into the target data format to obtain the converted data push request; modifying the parameters of the target field in the converted data push request to the preset debugging parameters to obtain the modified data push request; based on the modified data push request, generating a data push test request.
[0181] Among them, the target field refers to the field containing debug, and the preset debugging parameter refers to true, that is, debug = true. Since the data push request written by the various commonly used request protocols can be mainly converted into three data formats, namely Query parameters (a query parameter class), Json characters (JavaScript Object Notation, JS object notation, a lightweight data exchange format) and Pb strings (Protocol Buffer, an efficient method for serializing structured data). The Pb string needs to rely on the original request protocol to be parsed, so that the data push request can be modified. Therefore, the target data format can be set to Query parameters and / or Json characters. Since Query parameters or Json characters are in keyvalue form (that is, fields and parameters correspond one to one), the data push request converted to the target data format only needs to modify the parameters of the target field to modify the data push request to the debugging state.
[0182] Furthermore, based on the modified data push request, the specific method of generating a data push test request can be: obtaining the push service type to which the specified push position belongs; based on the pre-established correspondence between the push service type and the request protocol, obtaining the request protocol corresponding to the push service type; based on the request protocol, processing the modified data push request to generate a data push test request.
[0183] Among them, based on the request protocol, the modified data push request is processed to generate a data push test request, that is, based on the format requirements specified in the request protocol, the modified data push request is rewritten to generate a data push test request.
[0184] In addition, the push service type belongs to the traffic attribute mentioned in the example of step S306. Since the request protocol is usually related to the push service type to which the specified push position belongs, and the modified data push request needs to be packaged into a request that can actually be initiated through the request protocol; therefore, it is necessary to find the corresponding request protocol to process the modified data push request in order to finally generate a data push test request.
[0185] It should be noted that the specific implementation method of generating the data push test request based on the acquired historical data push request in step S702 can refer to the specific implementation method of generating the data push test request based on the acquired historical data push request, which is not repeated here.
[0186] S704: respond to a data push test request for a designated push location, and obtain, through a push service platform, whiteboard data generated during a recall process of push data from a push database to the designated push location.
[0187] In the embodiment of the present application, since the server needs to initiate a data push test request before responding to the data push test request, before step S704, the push service type to which the specified push position belongs can also be obtained; based on the pre-established correspondence between the push service type and the request protocol, the request protocol corresponding to the push service type can be obtained; based on the pre-established correspondence between the request protocol and the packet issuance protocol, the packet issuance protocol corresponding to the request protocol can be obtained; based on the packet issuance protocol, a data push test request can be initiated.
[0188] Specifically, the request protocol is usually related to the push service type to which the specified push position belongs, and the packet sending protocol is associated with the request protocol. Therefore, it is necessary to find the corresponding request protocol according to the push service type to which the specified push position belongs, and then find the appropriate packet sending protocol according to the request protocol. In a specific implementation, the packet sending protocol corresponding to the request protocol can be a packet sending protocol such as Hyper Text Transfer Protocol (HTTP), Remote Procedure Call (RPC) or svrkitrpc (a remote transmission protocol independently developed based on RPC).
[0189] In addition, the specific implementation of obtaining whiteboard data in step S704 can refer to the specific implementation of step S201 in the above embodiment, which will not be repeated here.
[0190] S705: Obtain a target push rule that matches the designated push position from multiple push rules through the diagnosis platform.
[0191] In the embodiment of the present application, the specific implementation of step S705 can refer to the specific implementation of step S202 and steps S302 to S304 in the above embodiment, which will not be repeated here.
[0192] S706: Acquire key data fields in the whiteboard data that match the target push rule.
[0193] In the embodiment of the present application, the specific implementation of step S706 can refer to the specific implementation of step S203 in the above embodiment, which will not be repeated here.
[0194] S707. If the semantics of the key data field does not match the push logic indicated by the target push rule, it is determined that the push data is not pushed to the designated push location, and a recall diagnosis result that the push data is not pushed to the designated push location is generated according to the push logic indicated by the target push rule.
[0195] In the embodiment of the present application, the specific implementation of step S707 can refer to the specific implementation of step S204 in the above embodiment, which will not be repeated here.
[0196] S708: Output the recall diagnosis result of the pushed data.
[0197] In the embodiment of the present application, the specific implementation of step S708 can refer to the specific implementation of step S205 and step S307 in the above embodiment, which will not be repeated here.
[0198] In the embodiment of the present application, a data push test request can be automatically generated based on the historical data push request found, so that the debugging personnel do not need to manually modify the data push request to the debugging state, which is conducive to improving the troubleshooting efficiency and reducing the time, labor and other troubleshooting costs. In addition, in the embodiment of the present application, a data push test request can be independently initiated by finding a contracting protocol suitable for the specified push position, which is conducive to further improving the troubleshooting efficiency and reducing the time, labor and other troubleshooting costs.
[0199] In one embodiment of the present application, another data processing system for pushing data recall is provided, which can be seen in Figure 8 , Figure 8 The data processing system for push data recall shown may include a terminal device 801, a diagnostic server 802 and a push server 803. A communication connection is established between the diagnostic server and the terminal device, and a communication connection is established between the push server and the diagnostic server.
[0200] The terminal device 801 may include any one or more of a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart TV (TV), a smart car, and a smart wearable device. The terminal device 801 runs a diagnostic platform, and may also run a multimedia player client, a social client, a browser client, etc., without limitation.
[0201] A diagnostic platform is running in the diagnostic server 802. The diagnostic server 802 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and basic cloud computing services such as big data and artificial intelligence platforms. A push service platform is running in the push server 803. The push server 803 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and basic cloud computing services such as big data and artificial intelligence platforms. The terminal device 801 and the diagnostic server 802, as well as the diagnostic server 802 and the push server 803 can be directly or indirectly connected in communication via wired or wireless communication, and this application is not limited here.
[0202] In one embodiment of the present application, another data processing method for push data recall is provided, and the data processing method for push data recall can be applied to Figure 8 The data processing system for push data recall shown in the figure can be jointly executed by the terminal device, the diagnostic server and the push server. In the embodiment of the present application, the method is described by taking the method executed by the diagnostic platform running in the diagnostic server and the push service platform running in the push server as an example. Fig. 9 As shown, a flowchart of another method for processing push data recall is shown. S901 to S910 are described in detail as follows:
[0203] S901. The diagnosis platform obtains a historical data push request initiated by a designated object through a designated push location found in an object database.
[0204] In an embodiment of the present application, the diagnostic platform can first receive the object identification information of the specified object and the push position identification information of the specified push position sent by the terminal device, and then the diagnostic platform searches the object request database for the historical data push request initiated by the specified object through the specified push position based on the object identification information and the push position identification information.
[0205] In addition, a diagnostic platform client is running in the terminal device, and the diagnostic platform client may include a push configuration interface. The terminal device may then respond to the debugger's editing and selection operations on the push configuration interface to obtain object identification information of the specified object and push position identification information of the specified push position.
[0206] In addition, the specific implementation of step S901 can refer to the specific implementation of step S701 and step S702, which will not be described in detail here.
[0207] S902: The diagnostic platform generates a data push test request for a specified push location based on the found historical data push request.
[0208] In the embodiment of the present application, the specific implementation of the diagnostic platform generating the data push test request can refer to the specific implementation of step S703, which will not be described in detail here.
[0209] Optionally, the push service platform running in the push server can provide a format conversion service for converting the data format of the data push request into the target data format. Then, the specific way for the diagnostic platform to generate a data push test request can be: the diagnostic platform sends the historical data push request found to the push service platform, and the push service platform calls the format conversion service to convert the data format of the historical data push request found into the target data format, and obtains the converted data push request; then, the diagnostic platform receives the converted data push request returned by the push service platform; thereafter, the diagnostic platform modifies the parameters of the target field in the converted data push request to the preset debugging parameters, and obtains the modified data push request; finally, the diagnostic platform generates a data push test request based on the modified data push request.
[0210] Among them, the specific method of generating a data push test request based on the modified data push request can be: obtaining the push service type to which the specified push position belongs; based on the pre-established correspondence between the push service type and the request protocol, obtaining the request protocol corresponding to the push service type; based on the request protocol, processing the modified data push request to generate a data push test request.
[0211] Optionally, the diagnostic platform may first determine whether the data format of the historical data push request found is the target data format. If not, the historical data push request found will be sent to the push service platform so that the push service platform can execute subsequent steps. If so, the diagnostic platform can directly modify the parameters of the target field in the historical data push request to the preset debugging parameters, obtain the modified data push request, and generate a data push test request based on the modified data push request.
[0212] In actual application, please refer to the attached Fig.10 , shows a schematic diagram of the process of generating a data push test request. The target data format can be set to Json. After the diagnostic platform running in the diagnostic server obtains the historical data push request, it will call Fig.10 The request standardization service shown sends the historical data push request to the push service platform in the push server. The push service platform calls the Pb / Json conversion service to convert the data format of the historical data push request into Json, and obtains the data push request in Json format.
[0213] In addition, if Fig.10 As shown, the protocol file of the push service platform stores the request protocols used by all push positions, and a corresponding relationship is established between the request protocols in the protocol file and the push service types. Therefore, the push service platform can also find the corresponding target request protocol according to the push service type to which the designated push position that initiates the historical data push request belongs, and send the target request protocol to the protocol adapter in the diagnostic platform. Optionally, the push service platform can send the target request protocol to the protocol adapter in the diagnostic platform through the Pb / Json conversion service.
[0214] like Fig.10 As shown, after the request standardization service in the diagnostic platform obtains the data push request in Json format, it will send the data push request in Json format to the protocol adapter. The protocol adapter will process the data push request in Json format according to the target request protocol sent by the received push service platform, and finally obtain the data push test request.
[0215] Specifically, the diagnostic platform in the diagnostic server can directly store multiple request protocols used by all push positions, and then convert, parse and process data push requests; but since the push service platform in the push server is the real platform for managing protocol files, the diagnostic platform can only store copies of protocol files. Once there is a request protocol update in the protocol file, the copy in the diagnostic platform will have an update delay, which may cause the diagnostic platform to fail to convert, parse and process (i.e., protocol consistency issues). Therefore, by adding a format conversion service in the push service platform, the success rate of generating data push test requests can be improved.
[0216] S903: The diagnosis platform sends a data push test request to the push service platform.
[0217] In an embodiment of the present application, the diagnostic platform can directly send the data push test request to the push service platform. Optionally, in order to further enhance data security, the diagnostic platform can first encrypt the data push test request, and then send the encrypted data push test request to the push service platform. Optionally, the data push test request can also be sent in other ways, which will not be described in detail here.
[0218] S904: The push service platform obtains the packet sending protocol corresponding to the specified push location.
[0219] In an embodiment of the present application, since the request protocol is usually related to the push service type to which the specified push position belongs, and the packet sending protocol is associated with the request protocol, it is necessary to find the corresponding request protocol according to the push service type to which the specified push position belongs, and then find a suitable packet sending protocol based on the request protocol.
[0220] Therefore, the specific method for the push service platform to obtain the package sending protocol corresponding to the designated push position can be: obtain the push service type to which the designated push position belongs; based on the pre-established correspondence between the push service type and the request protocol, obtain the request protocol corresponding to the push service type; based on the pre-established correspondence between the request protocol and the package sending protocol, obtain the package sending protocol corresponding to the request protocol.
[0221] S905: The push service platform initiates a data push test request based on the packet sending protocol.
[0222] In an embodiment of the present application, since the data push test request is used to obtain push data for a designated push position, and the push database and the push system for push data recall may not be running in the push service platform; therefore, the specific method for the push service platform to initiate a data push test request based on the contract sending agreement can be: the push service platform sends the data push test request to the destination server in accordance with the data transmission method indicated by the contract sending agreement, where the destination server runs a push database and a push system.
[0223] S906: The push service platform obtains the whiteboard data generated during the recall process of the push data from the push database to the designated push location.
[0224] In the embodiment of the present application, since step S201 mentions that the whiteboard data is included in the data reply packet, and step S905 mentions that the push database and the push system are running in the destination server; therefore, the push service platform can receive the data reply packet returned by the destination server to obtain the whiteboard data corresponding to the push data. Among them, the destination server responds to the data push test request, obtains the push data from the push database, and then processes the push data through the push system according to the arrangement order of each module in the push system, and obtains the processed data of each module during the processing to generate a data reply packet.
[0225] In addition, the specific implementation of obtaining whiteboard data in step S906 can also refer to the specific implementation of step S201 in the above embodiment, which will not be repeated here.
[0226] In actual application, please refer to the attached Fig.11 , which shows a schematic diagram of the process of obtaining a data response packet. The specific process of generating a data push test request can be found in Fig.10 The detailed description of the example is not repeated here.
[0227] like Fig.11 As shown, the diagnosis platform is integrated with a package agent module 1101, and the push service platform is integrated with a package service module 1102. The package service includes three package protocols: http, rpc and svrkitrpc.
[0228] After receiving the data push test request output by the protocol adapter, the package issuing agent module 1101 will send the data push test request to the package issuing service module 1102. The package issuing service module 1102 will receive the target request protocol sent by the protocol file and find the target package issuing protocol that is compatible with the target request protocol. Fig.11 As shown, the package sending service module 1102 will initiate a data push test request to the destination server 1103 according to the target package sending protocol.
[0229] Afterwards, the destination server 1103 will respond to the data push test request, obtain the push data from the push database, and then process the push data through the push system according to the arrangement order of each module in the push system, and obtain the processing data of each module during the processing to generate a data return packet. Finally, the packet sending service module 1102 receives the data return packet returned by the destination server 1103, and sends the data return packet to the packet sending agent module 1101 of the diagnosis platform, so that the diagnosis platform can obtain the recall diagnosis result of the push data based on the whiteboard data in the data return packet.
[0230] Similarly, by integrating the package sending service into the push service platform, the protocol consistency problem between the two platforms mentioned in step S902 can also be avoided, thereby improving the success rate of initiating the data push test request.
[0231] S907: The diagnosis platform receives the whiteboard data returned by the push service platform.
[0232] In the embodiment of the present application, the diagnosis platform may first receive a data response packet containing whiteboard data, and then obtain the whiteboard data by parsing the data response packet.
[0233] S908: The diagnosis platform obtains a target push rule that matches the specified push position from multiple push rules.
[0234] In the embodiment of the present application, the specific implementation of step S908 can refer to the specific implementation of step S202 and steps S302 to S304 in the above embodiment, which will not be repeated here.
[0235] S909: The diagnosis platform obtains key data fields in the whiteboard data that match the target push rule.
[0236] In the embodiment of the present application, the specific implementation of step S909 can refer to the specific implementation of step S203 in the above embodiment, which will not be repeated here.
[0237] S910. If the semantics of the key data field does not match the push logic indicated by the target push rule, the diagnostic platform determines that the push data is not pushed to the designated push location, and generates a recall diagnostic result that the push data is not pushed to the designated push location according to the push logic indicated by the target push rule.
[0238] In the embodiment of the present application, the specific implementation of step S910 can refer to the specific implementation of step S204 in the above embodiment, which will not be repeated here.
[0239] S911. The diagnostic platform outputs the recall diagnostic result of the pushed data.
[0240] In the embodiment of the present application, the specific implementation of step S911 can refer to the specific implementation of step S205 and step S307 in the above embodiment, which will not be repeated here.
[0241] In the embodiment of the present application, the data push test request is automatically generated through the diagnostic platform, so that the debugger does not need to manually modify the data push request to the debugging state, which is conducive to improving the troubleshooting efficiency and reducing the time, labor and other troubleshooting costs. In addition, in the embodiment of the present application, the push service platform can also find the contracting protocol suitable for the specified push position to independently initiate the data push test request, which is conducive to further improving the troubleshooting efficiency and reducing the time, labor and other troubleshooting costs.
[0242] In addition, the embodiment of the present application can effectively avoid protocol consistency problems by integrating the package sending service and format conversion service into the push service platform in the push server, so that the success rate of automatically obtaining whiteboard data is higher, which is beneficial to improving the overall troubleshooting efficiency and troubleshooting success rate.
[0243] Here, an apparatus embodiment of the present application is introduced, which can be used to execute the data processing method for push data recall in the above-mentioned embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the embodiment of the data processing method for push data recall in the above-mentioned embodiment of the present application.
[0244] The present application embodiment provides a data processing device for pushing data recall, such as Fig.12 As shown, the device includes an acquisition unit 1201, a processing unit 1202 and an output unit 1203, wherein:
[0245] The acquisition unit 1201 is used to respond to a data push test request for a designated push location and acquire whiteboard data generated during a recall process of push data from a push database to the designated push location through a push service platform;
[0246] The processing unit 1202 is used to obtain a target push rule matching the specified push position from a plurality of push rules through the diagnosis platform; different push rules indicate different push logics;
[0247] The processing unit 1202 is further used to obtain key data fields in the whiteboard data that match the target push rule;
[0248] The processing unit 1202 is further configured to determine that the pushed data is not pushed to the designated push location if the semantics of the key field of the data does not match the push logic indicated by the target push rule, and generate a recall diagnosis result that the pushed data is not pushed to the designated push location according to the push logic indicated by the target push rule;
[0249] The output unit 1203 is used to output the recall diagnosis result of the pushed data; the recall diagnosis result is used to prompt that the push logic that the pushed data is not pushed to the designated push location is not satisfied.
[0250] In one embodiment of the present application, based on the aforementioned scheme, when the processing unit 1202 obtains a target push rule that matches the designated push position from multiple push rules through a diagnostic platform, it can be specifically used to: obtain push range information of the designated push position through a diagnostic platform; wherein the push range information includes at least one of the following: associated push data of the designated push position, push position information of the designated push position, application identification information of the application to which the designated push position belongs, and environment identification information of the initiation environment in which the designated push position initiates the data push request; obtain candidate push rules from the multiple push rules, and adaptation range information of the candidate push rules; if the adaptation range information of the candidate push rule matches the push range information, the candidate push rule is determined as the target push rule.
[0251] In one embodiment of the present application, the multiple push rules are arranged in a preset order; based on the aforementioned scheme, when the processing unit 1202 obtains the target push rule that matches the specified push position from the multiple push rules through the diagnostic platform, it can be specifically used to: obtain the push range information of the specified push position through the diagnostic platform; select the push rules in sequence according to the arrangement order of the multiple push rules, and match the adaptation range information of the selected push rules with the push range information until the adaptation range information of the selected push rule matches the push range information; use the push rule whose adaptation range information matches the push range information as the target push rule.
[0252] In one embodiment of the present application, based on the aforementioned scheme, the processing unit 1202 can be further used to: splice the data key field with the target push rule to obtain a spliced text; perform semantic association recognition processing on the spliced text to obtain the semantic association between the data key field and the target push rule; if the semantic association is less than or equal to a preset association threshold, it is determined that the semantics of the data key field does not match the push logic indicated by the target push rule.
[0253] In one embodiment of the present application, based on the aforementioned scheme, the multiple push rules are arranged in a preset order; the processing unit 1202 can also be used for: if the semantics of the data key field matches the push logic indicated by the target push rule, then the push rule whose arrangement order is after the target push rule and matches the designated push position is used as the new target push rule; obtaining a new data key field in the whiteboard data that matches the new target push rule; when the semantics of the new data field does not match the push logic indicated by the new target push rule, determining that the push data is not pushed to the designated push position, and generating a recall diagnosis result for the push data according to the push logic indicated by the new target push rule.
[0254] In one embodiment of the present application, based on the aforementioned scheme, the acquisition unit 1201 can also be used to: obtain object identification information of a specified object, and push position information of the specified push position; according to the object identification information and the push position identification information, search from an object request database for historical data push requests initiated by the specified object through the specified push position; wherein the object request database is used to store historical data push requests initiated by multiple objects through multiple push positions; and generate the data push test request based on the found historical data push requests.
[0255] In one embodiment of the present application, based on the aforementioned scheme, the acquisition unit 1201 can also be used for: if the historical data push request initiated by the specified object through the specified push position is not found in the object request database, then obtaining a data push request matching the push position identification information from an online request database for storing historical data push requests initiated through multiple push positions; wherein the obtained data push request is used to obtain push data for the specified push position; and based on the obtained historical data push request, generating the data push test request.
[0256] In one embodiment of the present application, based on the aforementioned scheme, when the acquisition unit 1201 generates the data push test request based on the found historical data push request, it can be specifically used to: convert the data format of the found historical data push request into a target data format to obtain a converted data push request; modify the parameters of the target field in the converted data push request to preset debugging parameters to obtain a modified data push request; and generate the data push test request based on the modified data push request.
[0257] In one embodiment of the present application, based on the aforementioned scheme, when the acquisition unit 1201 generates the data push test request based on the modified data push request, it can be specifically used to: obtain the push service type to which the specified push position belongs; based on the pre-established correspondence between the push service type and the request protocol, obtain the request protocol corresponding to the push service type; based on the request protocol, process the modified data push request to generate the data push test request.
[0258] In one embodiment of the present application, the data processing device for push data recall also includes a request initiating unit 1204; based on the aforementioned scheme, the request initiating unit 1204 can be used to: obtain the push service type to which the designated push position belongs; based on a pre-established correspondence between the push service type and the request protocol, obtain the request protocol corresponding to the push service type; based on a pre-established correspondence between the request protocol and the packet sending protocol, obtain the packet sending protocol corresponding to the request protocol; based on the packet sending protocol, initiate the data push test request.
[0259] In one embodiment of the present application, based on the aforementioned scheme, when the acquisition unit 1201 responds to a data push test request for a designated push position and acquires the whiteboard data generated in the recall process of the push data from the push database to the designated push position through the push service platform, it can be specifically used to: send the data push test request to the push service platform so that the push service platform acquires the package sending protocol corresponding to the designated push position, initiates the data push test request based on the package sending protocol, and the push service platform acquires the whiteboard data; and receives the whiteboard data returned by the push service platform.
[0260] In one embodiment of the present application, based on the aforementioned scheme, when the output unit 1203 outputs the recall diagnosis result of the pushed data, it can be specifically used to: if the data push test request carries agent processing data, then the recall diagnosis result of the pushed data is sent to the agent processing platform, so that the agent processing platform obtains a push request modification method that matches the recall diagnosis result of the pushed data, and modifies the data push request initiated by the designated push position according to the push request modification method.
[0261] It should be noted that the device provided in the above embodiment and the method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment and will not be repeated here.
[0262] The device provided by the above embodiment can be arranged in a terminal device or in a server. The device provided by the embodiment of the present application can determine whether the semantics of the key data field in the whiteboard data matches the push logic indicated by the target push rule. When the semantics of the key data field does not match the push logic indicated by the target push rule, the recall diagnosis result of the push data can be directly generated according to the push logic indicated by the target push rule. It can be seen that the embodiment of the present application can autonomously find out the reasons why the push data cannot be recalled, avoiding the scene where the whiteboard data needs to be manually analyzed to troubleshoot the problem, greatly improving the efficiency of problem troubleshooting, and reducing the time, labor and other troubleshooting costs. At the same time, the embodiment of the present application will screen a plurality of push rules to a certain extent, and only the push rules that match the specified push position will be used as the target push rules for the next step of judgment; avoiding the situation where multiple fields in the whiteboard data need to be logically compared one by one with multiple push rules. Therefore, the embodiment of the present application can further improve the troubleshooting efficiency by accurately screening out the target push rules suitable for the specified push position.
[0263] An embodiment of the present application also provides an electronic device, comprising one or more processors and a storage device, wherein the storage device is used to store one or more computer programs, and when the one or more computer programs are executed by one or more processors, the electronic device implements the data processing method for push data recall as described above.
[0264] Fig.13 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown.
[0265] It should be noted that Fig.13 The computer system 1300 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0266] like Fig.13 As shown, the computer system 1300 includes a processor (Central Processing Unit, CPU) 1301, which can perform various appropriate actions and processes according to the program stored in the read-only memory (Read-Only Memory, ROM) 1302 or the program loaded from the storage part 1308 to the random access memory (Random Access Memory, RAM) 1303, such as executing the method in the above embodiment. In RAM 1303, various programs and data required for system operation are also stored. CPU 1301, ROM 1302 and RAM 1303 are connected to each other through bus 1304. Input / output (Input / Output, I / O) interface 1305 is also connected to bus 1304.
[0267] In some embodiments, the following components are connected to the I / O interface 1305: an input section 1306 including a keyboard, a mouse, etc.; an output section 1307 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to the I / O interface 1305 as needed. A removable medium 1311, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1310 as needed, so that a computer program read therefrom is installed into the storage section 1308 as needed.
[0268] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1309, and / or installed from a removable medium 1311. When the computer program is executed by a processor (CPU) 1301, various functions defined in the system of the present application are executed.
[0269] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (Erasable Programmable Read Only Memory), a flash memory, an optical fiber, a portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0270] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the devices, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and a computer program.
[0271] The units or modules involved in the embodiments described in this application may be implemented by software or hardware, and the units or modules described may also be set in a processor. The names of these units or modules do not, in some cases, constitute limitations on the units or modules themselves.
[0272] Another aspect of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the data processing method for recalling push data as described above is implemented. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.
[0273] Another aspect of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor of an electronic device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, so that the electronic device executes the data processing method for push data recall as described above in the above embodiments.
[0274] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.
[0275] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.
[0276] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person of ordinary skill in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.
Claims
1. A data processing method for push data recall, characterized in that: include: In response to a data push test request for a designated push location, the whiteboard data generated during the recall process of the push data from the push database to the designated push location is acquired through the push service platform; Acquire a target push rule matching the designated push position from a plurality of push rules through a diagnostic platform; different push rules indicate different push logics; Acquire key data fields in the whiteboard data that match the target push rule; If the semantics of the key field of the data does not match the push logic indicated by the target push rule, it is determined that the pushed data is not pushed to the designated push location, and a recall diagnosis result that the pushed data is not pushed to the designated push location is generated according to the push logic indicated by the target push rule; Outputting the recall diagnosis result of the pushed data; the recall diagnosis result is used to prompt that the pushed data is not pushed to the push logic that is not satisfied by the designated push location.
2. The method according to claim 1, characterized in that The step of obtaining a target push rule matching the designated push position from a plurality of push rules through the diagnosis platform includes: Acquire the push range information of the designated push position through the diagnostic platform; wherein the push range information includes at least one of the following: associated push data of the designated push position, push position information of the designated push position, application identification information of the application to which the designated push position belongs, and environment identification information of the initiation environment of the data push request initiated by the designated push position; Acquire candidate push rules and adaptation scope information of the candidate push rules from the multiple push rules; If the adaptation scope information of the candidate push rule matches the push scope information, the candidate push rule is determined as the target push rule.
3. The method according to claim 1, characterized in that: The multiple push rules are arranged in a preset order; the target push rule matching the specified push position is obtained from the multiple push rules through the diagnosis platform, including: Acquire the push range information of the designated push location through the diagnosis platform; Selecting push rules in sequence according to the arrangement order of the multiple push rules, and matching the adaptation scope information of the selected push rules with the push scope information until the adaptation scope information of the selected push rules matches the push scope information; The push rule whose adaptation scope information matches the push scope information is used as the target push rule.
4. The method according to claim 1, characterized in that The method further comprises: Splicing the data key field with the target push rule to obtain a spliced text; Performing semantic relevance recognition processing on the concatenated text to obtain the semantic relevance between the key data field and the target push rule; If the semantic relevance is less than or equal to a preset relevance threshold, it is determined that the semantics of the key data field does not match the push logic indicated by the target push rule.
5. The method according to claim 1, characterized in that The multiple push rules are arranged in a preset order; the method further includes: If the semantics of the data key field matches the push logic indicated by the target push rule, the push rule that is arranged after the target push rule and matches the designated push position is used as the new target push rule; Acquire a new data key field in the whiteboard data that matches the new target push rule; When the semantics of the new data field does not match the push logic indicated by the new target push rule, it is determined that the push data is not pushed to the designated push location, and a recall diagnosis result of the push data is generated according to the push logic indicated by the new target push rule.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Obtaining object identification information of a specified object and push position identification information of the specified push position; According to the object identification information and the push position identification information, searching the object request database for the historical data push request initiated by the designated object through the designated push position; wherein the object request database is used to store the historical data push requests initiated by multiple objects through multiple push positions; The data push test request is generated based on the found historical data push request.
7. The method according to claim 6, characterized in that The method further comprises: If the historical data push request initiated by the specified object through the specified push position is not found in the object request database, then obtaining a historical data push request matching the push position identification information from an online request database for storing historical data push requests initiated through multiple push positions; wherein the obtained historical data push request is used to obtain push data for the specified push position; The data push test request is generated based on the acquired historical data push request.
8. The method according to claim 6, characterized in that The step of generating the data push test request based on the found historical data push request includes: Convert the data format of the found historical data push request into a target data format to obtain a converted data push request; Modifying the parameters of the target field in the converted data push request to preset debugging parameters to obtain a modified data push request; Based on the modified data push request, the data push test request is generated.
9. The method according to claim 8, characterized in that The step of generating the data push test request based on the modified data push request includes: Obtaining the push service type to which the designated push location belongs; Based on the pre-established correspondence between the push service type and the request protocol, obtaining the request protocol corresponding to the push service type; Based on the request protocol, the modified data push request is processed to generate the data push test request.
10. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Obtaining the push service type to which the designated push location belongs; Based on the pre-established correspondence between the push service type and the request protocol, obtaining the request protocol corresponding to the push service type; Based on the pre-established correspondence between the request protocol and the contract issuing protocol, obtaining the contract issuing protocol corresponding to the request protocol; Based on the packet sending protocol, the data push test request is initiated.
11. The method according to any one of claims 1 to 5, characterized in that: The responding to the data push test request for the designated push position, obtaining the whiteboard data generated in the recall process of the push data from the push database to the designated push position through the push service platform, includes: Sending the data push test request to the push service platform, so that the push service platform obtains the package sending protocol corresponding to the designated push position, initiating the data push test request based on the package sending protocol, and the push service platform obtains the whiteboard data; Receive the whiteboard data returned by the push service platform.
12. The method according to any one of claims 1 to 5, characterized in that: The outputting of the recall diagnosis result of the pushed data includes: If the data push test request carries proxy processing information, the recall diagnosis result of the pushed data will be sent to the proxy processing platform, so that the proxy processing platform can obtain a push request modification method that matches the recall diagnosis result of the pushed data, and modify the data push request initiated by the designated push position according to the push request modification method.
13. A data processing device for push data recall, characterized in that: It includes an acquisition unit, a processing unit and an output unit, wherein: The acquisition unit is used to respond to a data push test request for a designated push location, and acquire the whiteboard data generated during the recall process of the push data from the push database to the designated push location through the push service platform; The processing unit is used to obtain a target push rule matching the specified push position from a plurality of push rules through a diagnostic platform; different push rules indicate different push logics; The processing unit is further used to obtain the key data field in the whiteboard data that matches the target push rule; The processing unit is further configured to determine that the pushed data is not pushed to the designated push location if the semantics of the key field of the data does not match the push logic indicated by the target push rule, and generate a recall diagnosis result that the pushed data is not pushed to the designated push location according to the push logic indicated by the target push rule; The output unit is used to output the recall diagnosis result of the pushed data; the recall diagnosis result is used to prompt that the pushed data is not pushed to the push logic that is not satisfied by the designated push position.
14. A computer storage medium, characterized in that: The computer storage medium stores one or more computer programs, and the one or more computer programs are suitable for being loaded by a processor and executing the data processing method for push data recall according to any one of claims 1 to 12.
15. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the data processing method for push data recall as described in any one of claims 1 to 12.
16. A computer program product, characterized in that The computer program product comprises a computer program, and the computer program is suitable for being loaded by a processor and executing the data processing method for push data recall according to any one of claims 1 to 12.
Citation Information
Patent Citations
Data detection method and device
CN105959180A
Evaluation method and device, computer equipment and storage medium
CN114706886A
History collection device, recommendation device, history collection method, and computer-readable recording medium
WO2012127757A1
