Push message processing method and device and storage medium

Abstract

The invention provides a push message processing method and device and a storage medium, which can be applied to various scenes such as cloud technology, artificial intelligence, intelligent driving and the like. The method comprises the following steps: acquiring an operation processing request for a push message; the operation processing request is generated based on an operation message input in the chat interaction interface; analyzing the operation processing request, and obtaining an operation instruction identifier and an operation parameter corresponding to the operation instruction identifier; acquiring an operation processing result corresponding to the operation processing request from at least one target node related to the operation processing request in the push message link under the condition that the operation instruction identifier and the operation parameter respectively meet a preset operation triggering condition; and sending the operation processing result, so that the operation processing result is displayed on the chat interaction interface. Therefore, the processing flow of the push message is simplified, and the processing efficiency of the push message is improved.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a method, device and storage medium for processing push messages. Background Art

[0002] With the development of Internet communications, message push has become one of the main ways for application developers to send messages to user terminals.

[0003] However, for one-to-many message push forms such as broadcast and multicast, different push results will appear due to the different operating states of different user terminals. Therefore, the query and control of push messages for a single user terminal will be scattered in different stages. Related technologies, due to the complexity of the message push link, usually through professionals familiar with the push system architecture to query and control the push messages of user terminals, which will result in low processing efficiency of push messages. Summary of the invention

[0004] The present application provides a method, device and storage medium for processing a push message to solve at least one technical problem in the prior art.

[0005] On the one hand, the present application provides a method for processing a push message, comprising:

[0006] Obtaining an operation processing request for a push message; the operation processing request is generated based on an operation message input in a chat interaction interface;

[0007] Parsing the operation processing request to obtain an operation instruction identifier and an operation parameter corresponding to the operation instruction identifier;

[0008] When the operation instruction identifier and the operation parameter respectively meet the preset operation triggering conditions, acquiring the operation processing result corresponding to the operation processing request from at least one target node related to the operation processing request in the push message link;

[0009] The operation processing result is sent so that the operation processing result is displayed on the chat interaction interface.

[0010] On the other hand, a push message processing device is also provided, the device comprising:

[0011] A request acquisition module, used to acquire an operation processing request for a push message; the operation processing request is generated based on an operation message input in the chat interaction interface;

[0012] A parsing module, used for parsing the operation processing request, obtaining an operation instruction identifier and an operation parameter corresponding to the operation instruction identifier;

[0013] A result acquisition module, configured to acquire an operation processing result corresponding to the operation processing request from at least one target node related to the operation processing request in a push message link when the operation instruction identifier and the operation parameter respectively meet preset operation triggering conditions;

[0014] The sending module is used to send the operation processing result so that the operation processing result can be displayed on the chat interaction interface.

[0015] On the other hand, an electronic device is also provided, which includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement any of the push message processing methods described above.

[0016] On the other hand, a computer-readable storage medium is provided, in which at least one instruction or at least one program is stored, and the at least one instruction or the at least one program is loaded and executed by a processor to implement any of the above-mentioned push message processing methods.

[0017] On the other hand, a computer program product or a computer program is also provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes any of the above-mentioned push message processing methods.

[0018] The present application provides a method, device and storage medium for processing push messages, which have the following technical effects:

[0019] The embodiment of the present application obtains an operation processing request for a push message; the operation processing request is generated based on an operation message input in a chat interaction interface; the operation processing request is parsed to obtain an operation instruction identifier and an operation parameter corresponding to the operation instruction identifier; when the operation instruction identifier and the operation parameter respectively meet the preset operation triggering conditions, the operation processing result corresponding to the operation processing request is obtained from at least one target node related to the operation processing request in the push message link; the operation processing result is sent so that the operation processing result is displayed in the chat interaction interface. In this way, by combining the operation command identifier, the operation parameter and the chat interaction mode, the operator only needs to input the operation message in the chat interaction interface, and the processing operations such as query and control of the push message can be realized through the interactive form of the chat dialogue, and the specific implementation details are shielded. By obtaining the operation processing result returned by at least one target node, multi-dimensional data aggregation is realized, the understanding cost and use cost of the push message system framework for the operator are reduced, the push message processing flow is simplified, and the processing efficiency and convenience of push messages are improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions and advantages in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0021] Figure 1 It is a schematic diagram of the architecture of a push message processing system provided in an embodiment of the present application;

[0022] Figure 2 It is a flowchart of a method for processing a push message provided in an embodiment of the present application;

[0023] Figure 3 This is a partial process diagram of another push message processing method provided in an embodiment of the present application;

[0024] Figure 4 It is a schematic diagram of a registration process of a method provided in an embodiment of the present application;

[0025] Figure 5 It is a flowchart of a step of obtaining an operation processing result corresponding to an operation processing request provided by an embodiment of the present application;

[0026] Figure 6 It is a timing diagram involved in a process of querying push message attributes provided by an embodiment of the present application;

[0027] Figure 7It is a timing diagram involved in a process of querying a push result of a push message provided in an embodiment of the present application;

[0028] Figure 8 It is a timing diagram involved in a process of querying object attributes provided by an embodiment of the present application;

[0029] Fig. 9 This is a timing diagram involved in a process of stopping message push provided in an embodiment of the present application;

[0030] Fig.10 It is a timing diagram involved in an intervention message push process provided by an embodiment of the present application;

[0031] Fig.11 It is a structural block diagram of a push message processing device provided in an embodiment of the present application;

[0032] Fig.12 It is a hardware structure diagram of an electronic device provided by the present application for implementing the method provided by an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0034] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0035] In the related art, since the message push link is relatively complex, it is usually through professionals who are familiar with the push system architecture to query and control the push messages of the user terminal. In particular, for a message push platform that provides multi-tenant capabilities and external services, if the developer only knows the user identifier and push identifier, and does not have a complete understanding of the system architecture, it is not possible to obtain the message push status of the target account very quickly. This will lead to low processing efficiency of push messages.

[0036] In view of this, the present application provides a method, device and storage medium for processing push messages, in which an operation processing request for a push message is obtained; the operation processing request is generated based on an operation message input in a chat interaction interface; the operation processing request is parsed to obtain an operation instruction identifier and an operation parameter corresponding to the operation instruction identifier; when the operation instruction identifier and the operation parameter respectively meet the preset operation triggering conditions, the operation processing result corresponding to the operation processing request is obtained from at least one target node related to the operation processing request in the push message link; the operation processing result is sent so that the operation processing result is displayed in the chat interaction interface. In this way, by combining the operation command identifier, the operation parameter and the chat interaction mode, the operator only needs to input the operation message in the chat interaction interface, and the processing operations such as query and control of the push message can be realized through the interactive form of the chat dialogue, and the specific implementation details are shielded. By obtaining the operation processing result returned by at least one target node, multi-dimensional data aggregation is realized, the understanding cost and use cost of the push message system framework for the operator are reduced, the push message processing process is simplified, and the processing efficiency and convenience of push messages are improved.

[0037] The following describes an exemplary application of the push message processing method provided in the embodiment of the present application. The push message processing method provided in the embodiment of the present application can be implemented by various electronic devices. For example, it can be implemented by a server or a terminal alone, or it can be implemented by a terminal and a server in collaboration.

[0038] The embodiment of the present application is described by taking the collaborative implementation of the server and the terminal as an example, see Figure 1 , Figure 1 1 is a schematic diagram of the architecture of a push message processing system provided by an embodiment of the present application. The push message processing system may include a management terminal 110 corresponding to an application developer, a user terminal 120, a service node 130, and a message processing server 140.

[0039] Among them, the management terminal 110, the user terminal 120 and the service node 130 can constitute a push message link. The number of service nodes 130 can be one or more, and different service nodes can correspond to the same processing function or storage function, or correspond to at least partially different processing functions or storage functions. Exemplarily, the application developer can send a push message to the user terminal 120 through the management terminal 110. During the message push process, the service node 130 can provide corresponding push services or management for the push message. The message processing server 140 is used to perform processing such as query or control on the push message on the push message link.

[0040] In some embodiments, the management terminal 110 or the user terminal 120 includes but is not limited to a mobile phone, a computer, an intelligent voice interaction device, a smart home appliance, a vehicle terminal, an aircraft, etc. The management terminal 110 or the user terminal 120 installs and runs an application that supports a chat function.

[0041] The service node 130 or the message processing server 140 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud 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, CDN (Content Delivery Network) and big data and artificial intelligence platforms. The service node 130 or the message processing server 140 is used to provide background services for the processing of push messages. The management terminal 110, the user terminal 120, the service node 130 and the message processing server 140 can be directly or indirectly connected through wired or wireless communication, and this application does not limit this.

[0042] In some embodiments, the service node 130 or the message processing server 140 can also be implemented as a node in a blockchain system. Blockchain is a new application model of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the blockchain underlying platform, the platform product service layer, and the application service layer.

[0043] In some embodiments, the embodiments of the present application can be implemented with the help of cloud technology (Cloud Technology). Cloud technology refers to a hosting technology that unifies a series of resources such as hardware, software, and network within a wide area network or a local area network to achieve data calculation, storage, processing, and sharing.

[0044] Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, and application technology based on the cloud computing business model. It can form a resource pool that can be used on demand and is flexible and convenient. Cloud computing technology will become an important support. The background services of the technical network system require a large amount of computing and storage resources.

[0045] It should be noted that this application involves user information and other related data. When the following embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0046] Figure 2 This is a flowchart of a method for processing a push message provided by an embodiment of the present application. This application provides method operation steps as described in the embodiment or flowchart, but more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps listed in the embodiment is only one way of executing the order of many steps and does not represent the only execution order. The execution subject of the method for processing a push message may be an electronic device, wherein the execution subject is the above-mentioned Figure 1 The message processing server in is used as an example to illustrate. Figure 2 As shown, the method may include:

[0047] S201: Obtain an operation processing request for a push message; the operation processing request is generated based on an operation message input in the chat interaction interface.

[0048] The operation processing request is a request for performing operations on a push message, including but not limited to data query, command execution, etc. For example, data query may include but not limited to querying the attributes of a push message, querying the push result of a push message for a push account object, querying the object attributes of a push account object, etc. Command execution may include but not limited to stopping message push, intervening in message push, etc.

[0049] The chat interaction interface may be a terminal interface corresponding to the request initiator of the operation processing request, and the chat interaction interface may be a page displayed in the client, a pop-up window, or a web page, etc. The request initiator may not be limited to professionals familiar with the push system architecture, but may also include but not limited to product personnel, operation personnel, and other personnel who are not familiar with the push system architecture.

[0050] The operation message may be input by the request initiator in the chat interaction interface through a keyboard, voice, or other forms. The operation message may be similar to an operation command line, which may include an operation instruction identifier and an operation parameter corresponding to the operation instruction identifier. The operation instruction identifier may include a system default instruction or a custom instruction. The operation parameter is an attribute parameter required to execute the operation instruction identifier.

[0051] Specifically, the operation instruction identifier may include a method name. Exemplarily, for a qt operation instruction, its operation instruction identifier is a method name of "qt", and the qt operation instruction is used to read task information according to a task ID. The task ID is the operation parameter corresponding to the qt operation instruction identifier, and the task ID may be a push message identifier, an object identifier, and the like. For a qm operation instruction, its operation instruction identifier is a method name of "qm", and the qm operation instruction is used to read material information according to a material ID. The material ID is the operation parameter corresponding to the qm operation instruction identifier, and the material ID refers to the identification identifier of the material contained in the push message. For a qpcl operation instruction, its operation instruction identifier is a method name of "qpcl", and the qpcl operation instruction is used to read the push log of a certain push object of the push center, and the object identifier of the push object is the operation parameter corresponding to the qpcl operation instruction identifier. For a utq operation instruction identifier, its operation instruction identifier is a method name of "utq", and the utq operation instruction is used to obtain the object tag of a certain account object, and the object identifier of the account object is the operation parameter corresponding to the utq operation instruction identifier.

[0052] Optionally, the chat interaction interface can be an intelligent dialogue interface for push messages between the request initiating object and the chat robot of the application, and rapid management such as query and control of push messages can be implemented in the chat interaction interface. Specifically, the request initiating object can enter the operation instruction identifier and the corresponding operation parameters in the chat interaction interface, and can enter the method name (e.g., qt) and task ID (e.g., 9***9) of the operation instruction, and display the operation message (e.g., qt 9***9) corresponding to the operation instruction identifier and the operation parameters. The chat robot obtains the operation message and generates an operation processing request based on the operation message entered in the chat interaction interface, sends the operation processing request to the message processing server, and responds to the operation processing request through the message processing server and triggers the execution of corresponding push message query or control and other management.

[0053] S203: Parse the operation processing request, and obtain the operation instruction identifier and the operation parameters corresponding to the operation instruction identifier.

[0054] Optionally, after obtaining the operation processing request, the operation processing request may be parsed to obtain the operation instruction identifier and the operation parameter corresponding to the operation instruction identifier contained in the operation processing request. For example, the operation instruction identifier (such as qt) and the corresponding operation parameter (such as 9***9) are parsed from the operation processing request.

[0055] In some embodiments, the preset operation trigger condition includes a first operation trigger condition corresponding to the operation instruction identifier and a second operation trigger condition corresponding to the operation parameter; after obtaining the operation instruction identifier and the operation parameter corresponding to the operation instruction identifier, the method further includes:

[0056] If there is a method implementation logic corresponding to the operation instruction identifier, determining that the operation instruction identifier satisfies the first operation triggering condition;

[0057] If the operation parameter satisfies the legality condition, it is determined that the operation instruction identifier satisfies the second operation triggering condition.

[0058] Optionally, if there is a method implementation logic corresponding to the operation instruction identifier, it indicates that there is a registered operation method for the operation instruction identifier, and it is determined that the operation instruction identifier meets the first operation trigger condition. If the operation parameter meets the legality condition, it indicates that the operation parameter is a valid parameter, and it is determined that the operation instruction identifier meets the second operation trigger condition. When the first operation trigger condition and the second operation trigger condition are met at the same time, it is determined that the operation instruction identifier and the operation parameter meet the preset operation trigger condition, and the corresponding processing can be performed based on the method implementation logic and the corresponding operation parameter corresponding to the operation instruction identifier. In this way, by detecting the method implementation logic and the operation parameter corresponding to the operation instruction identifier in advance, the execution of invalid processing requests can be avoided, and the processing efficiency of push messages and the utilization of computing resources can be improved.

[0059] In some embodiments, after obtaining the operation instruction identifier and the operation parameter corresponding to the operation instruction identifier, the method further includes:

[0060] If there is no method implementation logic corresponding to the operation instruction identifier, it is determined that the operation instruction identifier does not meet the first operation triggering condition;

[0061] Sending instruction list auxiliary information for the operation instruction identifier so that the instruction list auxiliary information is displayed on the chat interaction interface;

[0062] or,

[0063] If the operation parameter is empty or does not meet the legality condition, determine that the operation instruction identifier does not meet the second operation triggering condition;

[0064] Send instruction parameter prompt information for the operation parameters so that the instruction parameter prompt information is displayed on the chat interaction interface.

[0065] Alternatively, if Figure 3 As shown, the execution of the method corresponding to the operation instruction identifier is mainly triggered by the request initiating object. When the request initiating object enters the operation instruction identifier (such as method name) and operation parameters in the chat interaction interface, the chat robot sends an operation processing request to the message processing server. The message processing server parses the operation instruction identifier (such as method name) and operation parameters from the operation processing request according to the specified format, and searches the method registrar for the method implementation logic corresponding to the operation instruction identifier.

[0066] If there is a corresponding method to implement the logic and detect that the operation parameters are not empty and meet the legality conditions, determine that the operation instruction identifier meets the first operation trigger condition, and determine that the operation instruction identifier meets the second operation trigger condition, that is, determine that the operation instruction identifier and the operation parameters meet the preset operation trigger conditions respectively, so as to execute subsequent steps, such as executing corresponding instruction processing, and returning the operation processing result to the message processing server. The message processing server returns the operation processing result to the chat robot and displays it on the chat interaction interface.

[0067] If there is no corresponding method implementation logic, it is determined that the operation instruction identifier does not meet the first operation trigger condition, and the request initiator will be informed of the output error by returning an error message and attaching the instruction list auxiliary information for the operation parameters. The instruction list auxiliary information includes the currently supported method list, so that the instruction parameter prompt information is displayed on the chat interaction interface, thereby quickly guiding the request initiator to correctly use the corresponding function, further improving the processing efficiency of push messages.

[0068] If there is a corresponding method implementation logic, but the detected operation parameter is empty or does not meet the legality condition, it is determined that the operation instruction identifier does not meet the second operation trigger condition, and the instruction parameter prompt information for the operation parameter is sent. The instruction parameter prompt information includes help information for the instruction parameter, so that the instruction parameter prompt information is displayed on the chat interaction interface, thereby quickly guiding the request initiator to correctly use the corresponding function, further improving the processing efficiency of push messages.

[0069] In some embodiments, after obtaining the operation processing request for the push message, the method further includes:

[0070] Obtain the operation permission detection result of the request initiating object of the operation processing request;

[0071] When the operation authority detection result indicates that the preset operation authority conditions are not met, the operation authority prompt information is sent as the operation processing result corresponding to the operation processing request, so that the operation authority prompt information used to characterize insufficient operation authority is displayed on the chat interaction interface.

[0072] Optionally, the object identifier of the request initiating object of the operation processing request can be obtained, and the object identifier can be sent to the authority management system to trigger the acquisition of the operation authority detection result sent by the authority management system. The authority management system can store the correspondence between the object identifier of the request initiating object and the operation instruction identifier in the corresponding operation processing request, and can also store the correspondence between the object identifier of the request initiating object and the operation instruction identifier and operation parameters in the corresponding operation processing request. Then, the operation authority detection result is verified. When the operation authority detection result indicates that the preset operation authority condition is not met, the operation authority prompt information is used as the operation processing result corresponding to the operation processing request, and the operation authority prompt information used to characterize the insufficient operation authority is sent to the chat robot, so that the operation authority prompt information is displayed on the chat interaction interface, and there is no need to execute the subsequent push message processing steps. In this way, by limiting the operation authority threshold of the request initiating object, the security and reliability of push message processing are improved.

[0073] S205: When the operation instruction identifier and the operation parameters respectively meet the preset operation triggering conditions, an operation processing result corresponding to the operation processing request is obtained from at least one target node related to the operation processing request in the push message link.

[0074] Among them, the target node is the node involved in the push message link for executing the operation processing request. For different operation processing requests, it can correspond to the same target node or at least partially different target nodes. Exemplarily, for operation processing request 1, the corresponding target nodes are node 1 and node 2. For operation processing request 2, the corresponding target nodes are node 3 and node 4. For operation processing request 3, the corresponding target nodes are node 1, node 2 and node 3. For operation processing request 4, the corresponding target nodes are node 1 and node 2.

[0075] Optionally, when it is determined that the operation instruction identifier and the operation parameters satisfy the preset operation triggering conditions, at least one target node related to the operation processing request is determined from the push message link. The operation parameters are passed to the specific method implementation logic corresponding to the operation instruction identifier, and the corresponding method implementation logic is executed by each target node, and the operation processing results corresponding to the operation processing request are sent respectively.

[0076] S207: Send the operation processing result so that the operation processing result is displayed on the chat interaction interface.

[0077] Optionally, the operation processing results returned by each target node may be assembled successfully and then sent to the chat robot so that the operation processing results can be displayed on the chat interaction interface.

[0078] In some embodiments, the method further comprises:

[0079] In response to a method registration request for a push message, obtaining an operation method to be registered;

[0080] If there is no registered method implementation logic for the method name corresponding to the operation method to be registered, register the operation method to be registered in the method registrar;

[0081] If the method name corresponding to the operation method to be registered has a registered method implementation logic, a method registration failure message is sent.

[0082] Alternatively, if Figure 4 As shown, check whether there is a registered method implementation logic for the method name corresponding to the operation method to be registered. If not, that is, there is no registered method implementation logic for the method name corresponding to the operation method to be registered, register the operation method to be registered in the method registrar; if yes, that is, there is a registered method implementation logic for the method name corresponding to the operation method to be registered, send a method registration failure message. Since the management of methods is based on method names, each method name only supports one specific method implementation logic. When the same method name is registered repeatedly, a registration failure error message will be sent. If there is no repeated registration for the operation method to be registered, register the operation method to be registered in the method registrar. In this way, multiple method implementation logics are implemented through method registration to meet the diverse processing or control requirements for push messages and improve the processing flexibility of push messages.

[0083] The operation method to be registered can be a newly added method implementation logic for push messages. The operation method to be registered can be other methods except the operation method corresponding to the above operation instruction identifier, such as the pp (push profile) method for obtaining push message attributes, the ps (push stop) method for stopping push messages, the pI (push intervention) method for intervening push messages, the uplr (user pushlist result) method for obtaining the push result of push messages, the up (user profile) method for querying object attributes, etc. These methods will be introduced in detail later.

[0084] In addition, the operation method to be registered can also be used to implement some other control logic corresponding methods. Exemplarily, the other control logic may include: a) adding new intervention strategies in push intervention, such as modifying the sending style and delaying sending; b) other operations on the push message ID status, such as starting, pausing, withdrawing, etc.; c) adding, deleting, and modifying the push message ID attributes, such as adding covered users and modifying priorities; d) adding, deleting, and modifying the attributes of account objects; adding, deleting, and modifying the newly added objects, such as adding, deleting, and modifying the user package, etc.

[0085] In some embodiments, Figure 5-Figure 10 As shown, obtaining the operation processing result corresponding to the operation processing request from at least one target node related to the operation processing request in the push message link includes:

[0086] S501: Based on the operation processing request, determine at least one target node related to the operation processing request from a push message link;

[0087] S503: Obtaining the initial operation processing results returned by each target node; the initial operation processing results are determined based on the method implementation logic and operation parameters corresponding to the operation instruction identifier;

[0088] S505: Encapsulate each initial operation processing result to obtain an operation processing result corresponding to the operation processing request.

[0089] Optionally, at least one target node related to the operation processing request is determined from the push message link. Exemplarily, the target node may be at least one of a push service node, a push management node, an object tag management node, an object operation management node, and a device attribute management node, etc. The operation processing request is sent to the corresponding target node to request the initial operation processing result returned by each target node, and the initial operation processing result is determined based on the method implementation logic and operation parameters corresponding to the operation instruction identifier. Different method implementation logics can have the same type of operation parameters (such as push message ID, object identifier, etc.), or can correspond to different types of operation parameters (such as intervention strategies, etc.). Each initial operation processing result returned by each target node is encapsulated in a preset format to obtain an operation processing result corresponding to the operation processing request, and the operation processing result is used to be displayed in the chat interaction interface through a chat robot. In this way, by handing over the operation processing request to the matching target node in the push message link for processing, and encapsulating the initial operation processing result returned by each target node to obtain the operation processing result, the comprehensiveness of the obtained operation processing result is guaranteed, and the processing accuracy and processing efficiency of the push message are improved.

[0090] In some embodiments, when the operation processing request includes a first operation processing request for querying a push message attribute, at least one target node includes a push service node and a push management node, and the operation parameter includes a first push message identifier. At this time, the above step S503, obtaining the initial operation processing results returned by each target node includes:

[0091] Based on the method implementation logic corresponding to the operation instruction identifier, generate a first query request for querying the push status and a second query request for querying the push parameter settings;

[0092] Sending a first query request to the push service node, obtaining a push status returned by the push service node based on the first query request and the first push message identifier as an initial operation processing result corresponding to the push service node;

[0093] A second query request is sent to the push management node, and the push parameter setting returned by the push management node based on the second query request and the first push message identifier is obtained as an initial operation processing result corresponding to the push management node.

[0094] Optionally, since the push link is relatively complex, the attributes of the push message, such as the current status and progress, parameter settings, etc., are maintained by different storages. Therefore, the query of the push message attributes needs to obtain the data returned by multiple target nodes and display it after aggregating the multi-party data. Figure 6 As shown, it shows the timing diagram involved in the process of querying push message attributes, which requires requesting the push service node to obtain the push status (such as current status and progress), and requesting the management node to obtain the push parameter settings of the push message ID, etc.

[0095] See also Figure 6 As shown, before querying the push message attributes, it is necessary to verify the operation permissions of the object initiating the request, and return and display the operation permission prompt information when the permission verification is insufficient, and end the subsequent process. In addition, it is also necessary to verify the legitimacy of the push message ID, and when the push message ID is verified to be illegal, an error message can be displayed in the chat interaction interface. Figure 6 In the two time sequence segments of permission check and push message ID legitimacy verification, the break tag is marked respectively. The break tag indicates that if this segment is executed, the rest of the sequence will be abandoned. That is, if the permission check indicates insufficient permission, the operation permission prompt message of insufficient permission verification is returned, and the subsequent time sequence is abandoned. If the legitimacy verification represented by the first object fails, the information that the user ID is illegal is returned, and the subsequent time sequence is abandoned.

[0096] Then, after the authority verification and the push message ID are both verified, the logic can be implemented based on the method corresponding to the operation instruction identifier to generate a first query request for querying the push status and a second query request for querying the push parameter setting; and the first query request is sent to the push service node to obtain the push status returned by the push service node based on the operation instruction identifier indicated by the first query request and the first push message identifier (i.e., the push message ID) as the initial operation processing result corresponding to the push service node; and the second query request is sent to the push management node to obtain the push parameter setting returned by the push management node based on the operation instruction identifier indicated by the second query request and the first push message identifier (i.e., the push message ID) as the initial operation processing result corresponding to the push management node. Then, the initial operation processing result corresponding to the push service node and the initial operation processing result corresponding to the push management node are aggregated and packaged to obtain the packaged operation processing result; and the packaged operation processing result is returned to the chat robot, and the packaged operation processing result is displayed in the chat interaction interface, such as displaying the push message attributes and status.

[0097] Exemplarily, the request data of the first operation processing request may include:

[0098] pp (push profile) + push message ID

[0099] Accordingly, the query result data returned including the push message attributes may include:

[0100] Push status: completed;

[0101] Push tags: sports

[0102] Issue style: red dot, fold-free,...

[0103] Push start time: 2023-XX-XX XX:XX:XX

[0104] Push end time: 2023-XX-XX XX:XX:XX

[0105] Number of successful pushes: XXX

[0106] Push failure reason: XXXXX

[0107] …

[0108] In this way, by triggering the sending of corresponding query requests to different target nodes, the push message attributes can be queried conveniently and quickly, the query path of the push message can be simplified, and the processing efficiency of the push message can be improved.

[0109] In some embodiments, when the operation processing request includes a second operation processing request for querying a push result of a push message for a first account object, at least one target node includes a push service node, and the operation parameter includes a first object identifier of the first account object. At this time, in the above step S503, obtaining the initial operation processing results returned by each target node includes:

[0110] Based on the method implementation logic corresponding to the operation instruction identifier, generate a third query request for querying the push result of the push message for the first account object;

[0111] Sending a third query request to the push service node;

[0112] In the case where the operation parameter also includes the push message identifier to be queried, obtaining a push result returned by the push service node based on the third query request, the first object identifier and the push message identifier to be queried as the initial operation processing result corresponding to the push service node;

[0113] When the operation parameters do not include the push message identifier to be queried, the push result of the push message of the day returned by the push service node based on the third query request and the first object identifier is obtained as the initial operation processing result corresponding to the push service node.

[0114] Alternatively, if Figure 7 As shown, before querying the push result of the push message for the first account object, it is necessary to verify the operation authority of the object initiating the request, and return and display the operation authority prompt information when the authority verification is insufficient, and end the subsequent process. In addition, it is also necessary to verify the legitimacy of the first object identifier. Taking the first object identifier as a user ID as an example, when the user ID is verified to be illegal, it can be displayed that the user ID is illegal. In addition, if the operation parameters also include the push message identifier to be queried, taking the push message identifier to be queried as a push message ID list as an example, it is also necessary to verify the legitimacy of each push message ID in the push message ID list, and when the push message ID is verified to be illegal, an error message that the push message ID list is illegal can be displayed in the chat interaction interface.

[0115] Figure 7 In the two timing segments of the permission check and the legality verification of the first object identifier, a break label is marked respectively. The break label indicates that if this segment is executed, the rest of the sequence will be abandoned, that is, if the permission check indicates insufficient authority, an operation permission prompt message of insufficient authority verification is returned, and the execution of subsequent timing sequences is abandoned; if the legality verification represented by the first object fails, information that the user ID is illegal is returned, and the execution of subsequent timing sequences is abandoned. Figure 7An option (opt) tag is marked in the timing segment part for the legitimacy verification of the push message ID list, and the option tag indicates that it contains a sequence that may or may not occur, that is, when the operation parameters also include the push message identifier to be queried, the sequence of the legitimacy verification of the push message ID list is executed, and when the operation parameters do not include the push message identifier to be queried, the sequence of the legitimacy verification of the push message ID list is not executed.

[0116] Next, after the authority verification, user ID, and push message ID list are all verified, a third query request for querying the push results of the push message for the first account object is generated based on the method implementation logic corresponding to the operation instruction identifier, and the third query request is sent to the push service node. From the user dimension, obtaining the push results of the push messages of the first account object within a period of time can be divided into two situations:

[0117] The first case: when the operation parameter also includes the push message identifier to be queried, the push result returned by the push service node based on the third query request, the first object identifier and the push message identifier to be queried is obtained as the initial operation processing result corresponding to the push service node. That is, the push message ID list is specified in the operation parameter, and the result returned by the request only pushes the push results in the list.

[0118] The second case: when the operation parameters do not include the push message identifier to be queried, the push result of the push message of the day returned by the push service node based on the third query request and the first object identifier is obtained as the initial operation processing result corresponding to the push service node. That is, when the push message ID list is not specified in the operation parameters, the request returns the result of all the push message IDs of the user on the day.

[0119] Figure 7 In the timing segment of the request push result, an alternative (Alt) tag is marked, and the alternative tag indicates a mutually exclusive choice between two or more sequences, that is, executing the sequence of the first case above, or executing the sequence of the second case.

[0120] Next, the initial operation processing result corresponding to the push service node is packaged to obtain a packaged operation processing result; the packaged operation processing result is returned to the chat robot, and the packaged operation processing result is displayed in the chat interaction interface, such as displaying the push result.

[0121] Exemplarily, the request data of the second operation processing request may include:

[0122] uplr (user push list result) The object ID of the first account object pushes message ID1, pushes ID2, pushes ID3...

[0123] Correspondingly, the query result data of the returned push result may include:

[0124] Push message ID1: Success

[0125] Push message ID2: Error reason

[0126] Push message ID3: Error reason

[0127] …

[0128] In this way, by triggering the sending of corresponding query requests to different target nodes, the push results of the push message for the first account object can be queried conveniently and quickly, the query path of the push results can be simplified, and the processing efficiency of the push messages can be improved.

[0129] In some embodiments, when the operation processing request includes a third operation processing request for querying the object attribute of the second account object, at least one target node includes an object tag management node, an object operation management node, and a device attribute management node, and the operation parameter includes the second object identifier of the second account object. At this time, the above step S503, obtaining the initial operation processing results returned by each target node includes:

[0130] Based on the method implementation logic corresponding to the operation instruction identifier, generate a fourth query request for querying the object tag corresponding to the second account object, a fifth query request for querying the application operation log corresponding to the second account object, and a sixth query request for querying the device attributes of the device used by the second account object;

[0131] Sending a fourth query request to the object tag management node, obtaining the object tag returned by the object tag management node based on the fourth query request and the second object identifier as the initial operation processing result corresponding to the push service node;

[0132] Sending a fifth query request to the object operation management node, obtaining an application operation log returned by the object operation management node based on the fifth query request and the second object identifier as an initial operation processing result corresponding to the object operation management node;

[0133] A sixth query request is sent to the device attribute management node, and the device attribute returned by the device attribute management node based on the sixth query request and the second object identifier is obtained as an initial operation processing result corresponding to the device attribute management node.

[0134] Optionally, during daily troubleshooting, some push problems are caused by user attributes, such as user hit experiments, user tags, user devices, etc. Figure 8As shown, it shows the sequence diagram involved in the process of querying object attributes. After the authority verification and user ID are verified, based on the method implementation logic corresponding to the operation instruction identifier, a fourth query request for querying the object tag corresponding to the second account object, a fifth query request for querying the application operation log corresponding to the second account object, and a sixth query request for querying the device attributes of the device used by the second account object are generated, and the corresponding query requests are sent to the corresponding target nodes respectively. The object tag management node queries the corresponding object tag based on the fourth query request and the second object identifier as the initial operation processing result corresponding to the push service node. The object operation management node queries the corresponding application operation log based on the fifth query request and the second object identifier as the initial operation processing result corresponding to the object operation management node. The device attribute management node queries the corresponding device attribute based on the sixth query request and the second object identifier as the initial operation processing result corresponding to the device attribute management node. Then, the initial operation processing results corresponding to each target node are encapsulated to obtain the encapsulated operation processing result; and the encapsulated operation processing result is returned to the chat robot, and the encapsulated operation processing result is displayed in the chat interaction interface, such as displaying object attribute information.

[0135] Exemplarily, the request data of the third operation processing request may include:

[0136] up(userprofile)User ID

[0137] Accordingly, the query result data of the returned object attributes may include:

[0138] Device attributes: mobile phone brand, mobile app version, operating system version…

[0139] Application operation logs: the last login time, the last login city, the page or specific content clicked in the mobile application...

[0140] Experimental situation: hit experiment A-group 1, experiment B-group 2…

[0141] Object tags: interests (such as sports, life, food, etc.), geographical location (such as City A, City B, etc.)

[0142] …

[0143] In this way, by triggering the sending of corresponding query requests for object attributes to different target nodes, the object attributes can be easily and quickly queried at one time, simplifying the query path of object attributes, helping to speed up problem troubleshooting efficiency and improve push message processing efficiency.

[0144] In some embodiments, when the operation processing request includes a fourth operation processing request for stopping message push, at least one target node includes a push service node or a push management node, and the operation parameter includes a second push message identifier. At this time, the above step S503, obtaining the initial operation processing results returned by each target node includes:

[0145] Generate a stop control request for stopping message push based on the method implementation logic corresponding to the operation instruction identifier;

[0146] Send a stop control request to the push management node, and obtain a push stop receipt returned by the push management node based on the stop control request and the second push message identifier as an initial operation processing result corresponding to the push management node;

[0147] A stop control request is sent to the push service node, and a push stop receipt returned by the push service node based on the stop control request and the second push message identifier is obtained as an initial operation processing result corresponding to the push service node.

[0148] Normally, for message push, sometimes it is necessary to stop and roll back some mistakenly pushed messages. However, for a platform that provides multi-tenant capabilities, if you want to stop a certain push message ID, you need to go through the following process: 1) Query the specific tenant to which the push message ID belongs; 2) The management console jumps to the management interface of the current tenant; 3) Search for the operation interface of the push message ID in the management interface; 4) Manually stop the push. Obviously, this process is cumbersome if done manually, and for operators who do not fully understand the platform, the cost of understanding and use is too high. Fig. 9 As shown, it shows the sequence diagram involved in the process of stopping message push. By encapsulating the operation method process of stopping push messages, only the push ID parameter is exposed, which simplifies the processing process of push messages and improves the processing efficiency of push messages.

[0149] See also Fig. 9 As shown, after the permission verification of the request initiating object and the push message ID are verified, the method implementation logic corresponding to the operation instruction identifier can be used to generate a stop control request for stopping message push. Then, a stop control request can be sent to the push management node so that the push management node executes a push stop on the second push message identifier (i.e., the push message ID) based on the operation instruction identifier indicated by the stop control request, and returns the corresponding push stop receipt as the initial operation processing result corresponding to the push management node. Alternatively, a stop control request can be sent to the push service node to obtain the push stop receipt returned by the push service node based on the operation instruction identifier indicated by the stop control request and the second push message identifier (i.e., the push message ID) as the initial operation processing result corresponding to the push service node.

[0150] Next, based on the initial operation processing result corresponding to the push service node and / or the initial operation processing result corresponding to the push management node, encapsulation processing is performed to obtain the encapsulated operation processing result; the encapsulated operation processing result is returned to the chat robot, and the encapsulated operation processing result is displayed in the chat interaction interface, such as displaying a stop success notification, displaying a stop failure notification, etc.

[0151] Exemplarily, the request data of the fourth operation processing request may include:

[0152] ps (push stop) Push message ID1 Push message ID2...

[0153] Correspondingly, the returned data for stopping message push may include:

[0154] Push message ID1: Success

[0155] Push message ID2: Failed

[0156] …

[0157] In this way, by triggering the sending of corresponding stop requests for push messages to different target nodes, message push can be stopped conveniently and quickly without manual push messages, simplifying the stop path of push messages, reducing the operating cost of stopping push messages, and improving the processing efficiency of push messages.

[0158] In some embodiments, when the operation processing request includes a fifth operation processing request for intervening in message push, at least one target node includes a push service node, and the operation parameters include a third push message identifier and a target message intervention strategy. At this time, the above step S503, obtaining the initial operation processing results returned by each target node includes:

[0159] Based on the method implementation logic corresponding to the operation instruction identifier, an intervention control request for intervention message push is generated; the intervention control request includes a target message intervention strategy;

[0160] An intervention control request is sent to the push service node, and a message intervention execution receipt is obtained, which is returned by the push service node based on the intervention control request, the third push message identifier and the target message intervention policy, as the initial operation processing result corresponding to the push service node; the message intervention execution receipt is at least used to characterize whether the push message corresponding to the third push message identifier is successfully intervened.

[0161] Alternatively, if Fig.10 As shown in Figure 1, it shows the sequence diagram involved in the intervention message push process. Fig.10As shown, after the permission verification of the request initiating object and the push message ID are verified, the logic can be implemented based on the method corresponding to the operation instruction identifier to generate an intervention control request for intervening in the message push; the intervention control request includes a target message intervention strategy. Exemplary intervention strategies may include, but are not limited to: such as rule filtering of user tags, device types, etc. in push messages, and the owner raising the push priority for a certain type of user. Then, an intervention control request can be sent to the push service node, so that the push service node performs a message intervention operation on the third push message identifier (i.e., the push message ID) based on the intervention strategy indicated by the intervention control request, and returns the corresponding message intervention execution receipt as the initial operation processing result corresponding to the push service node. The message intervention execution receipt is at least used to indicate whether the push message corresponding to the third push message identifier has been successfully intervened.

[0162] Next, the initial operation processing result corresponding to the push service node is encapsulated to obtain the encapsulated operation processing result; the encapsulated operation processing result is returned to the chat robot, and the encapsulated operation processing result is displayed in the chat interaction interface, such as displaying a successful intervention notification and intervention information, displaying an intervention failure notification, etc.

[0163] Exemplarily, the request data of the fifth operation processing request may include:

[0164] pl (push intervention) push ID 1 push ID 2 utm (user tag mask) tag A tag B… adm (active day) 120-365 90-120

[0165] Correspondingly, the returned data for stopping message push may include:

[0166] Push message ID1: Success

[0167] Push message ID2: Failed

[0168] In this way, by triggering the sending of corresponding intervention requests for push messages to different target nodes, it is possible to conveniently and quickly intervene in message push, reduce the operating cost of stopping push messages, and improve the processing efficiency of push messages. In the process of message push, the intervention strategy of push messages can be adjusted according to application requirements, reflecting the convenience and diversity of the push message platform, thereby improving the speed and flexibility of message push.

[0169] The above embodiment combines the operation command identifier, operation parameters and chat interaction method, and the operator only needs to input the operation message in the chat interaction interface, and the processing operations such as query and control of the push message can be realized through the interactive form of the chat dialogue, shielding the specific implementation details, and by obtaining the operation processing result returned by at least one target node, multi-dimensional data aggregation is realized, which reduces the operator's understanding cost and use cost of the push message system framework, simplifies the push message processing process, and improves the processing efficiency and ease of use of push messages.

[0170] The following is an embodiment of the device of the present application, which can be used to perform the steps in the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0171] Fig.11 is a structural block diagram of a push message processing device provided in an embodiment of the present application. The push message processing device has the functions of implementing the above method example, and the functions can be implemented by hardware or by hardware executing corresponding software. Fig.11 As shown, a push message processing device may include:

[0172] The request acquisition module 1110 is used to acquire an operation processing request for a push message; the operation processing request is generated based on an operation message input in the chat interaction interface;

[0173] The parsing module 1120 is used to parse the operation processing request and obtain the operation instruction identifier and the operation parameters corresponding to the operation instruction identifier;

[0174] The result acquisition module 1130 is used to acquire the operation processing result corresponding to the operation processing request from at least one target node related to the operation processing request in the push message link when the operation instruction identifier and the operation parameters respectively meet the preset operation triggering conditions;

[0175] The sending module 1140 is used to send the operation processing result so that the operation processing result can be displayed on the chat interaction interface.

[0176] In some embodiments, the preset operation trigger condition includes a first operation trigger condition corresponding to the operation instruction identifier and a second operation trigger condition corresponding to the operation parameter; the device further includes:

[0177] A first detection module, configured to determine that the operation instruction identifier satisfies a first operation triggering condition if there is a method implementation logic corresponding to the operation instruction identifier;

[0178] The second detection module is used to determine whether the operation instruction identifier meets the second operation triggering condition if the operation parameter meets the legality condition.

[0179] In some embodiments, the apparatus further comprises:

[0180] A third detection module, configured to determine that the operation instruction identifier does not satisfy the first operation trigger condition if there is no method implementation logic corresponding to the operation instruction identifier;

[0181] A fourth detection module, used for sending instruction list auxiliary information for the operation instruction identifier, so that the instruction list auxiliary information is displayed on the chat interaction interface;

[0182] or,

[0183] A fifth detection module, configured to determine that the operation instruction identifier does not satisfy the second operation triggering condition if the operation parameter is empty or does not satisfy the legality condition;

[0184] The sixth detection module is used to send instruction parameter prompt information for the operation parameters so that the instruction parameter prompt information is displayed on the chat interaction interface.

[0185] In some embodiments, the apparatus further comprises:

[0186] The permission result acquisition module is used to obtain the operation permission detection result of the request initiating object of the operation processing request;

[0187] The permission prompt sending module is used to send the operation permission prompt information as the operation processing result corresponding to the operation processing request when the operation permission detection result indicates that the preset operation permission conditions are not met, so that the operation permission prompt information used to characterize insufficient operation permission is displayed on the chat interaction interface.

[0188] In some embodiments, the apparatus further comprises:

[0189] A method acquisition module, used to respond to a method registration request for a push message and acquire an operation method to be registered;

[0190] A method registration module is used to register the operation method to be registered in the method registrar if there is no registered method implementation logic for the method name corresponding to the operation method to be registered;

[0191] The registration failure sending module is used to send method registration failure information if the method name corresponding to the operation method to be registered has a registered method implementation logic.

[0192] In some embodiments, the result acquisition module 1130 includes:

[0193] A node determination submodule, configured to determine at least one target node related to the operation processing request from a push message link based on the operation processing request;

[0194] The result acquisition submodule is used to obtain the initial operation processing results returned by each target node; the initial operation processing results are determined based on the method implementation logic and operation parameters corresponding to the operation instruction identifier;

[0195] The encapsulation submodule is used to encapsulate each initial operation processing result to obtain an operation processing result corresponding to the operation processing request.

[0196] In some embodiments, when the operation processing request includes a first operation processing request for querying a push message attribute, the at least one target node includes a push service node and a push management node, and the operation parameter includes a first push message identifier; the result acquisition submodule is specifically used to:

[0197] Based on the method implementation logic corresponding to the operation instruction identifier, generate a first query request for querying the push status and a second query request for querying the push parameter settings;

[0198] Sending a first query request to the push service node, obtaining a push status returned by the push service node based on the first query request and the first push message identifier as an initial operation processing result corresponding to the push service node;

[0199] A second query request is sent to the push management node, and the push parameter setting returned by the push management node based on the second query request and the first push message identifier is obtained as an initial operation processing result corresponding to the push management node.

[0200] In some embodiments, when the operation processing request includes a second operation processing request for querying a push result of a push message for a first account object, the at least one target node includes a push service node, and the operation parameter includes a first object identifier of the first account object; the result acquisition submodule is specifically used to:

[0201] Based on the method implementation logic corresponding to the operation instruction identifier, generate a third query request for querying the push result of the push message for the first account object;

[0202] Sending a third query request to the push service node;

[0203] In the case where the operation parameter also includes the push message identifier to be queried, obtaining a push result returned by the push service node based on the third query request, the first object identifier and the push message identifier to be queried as the initial operation processing result corresponding to the push service node;

[0204] When the operation parameters do not include the push message identifier to be queried, the push result of the push message of the day returned by the push service node based on the third query request and the first object identifier is obtained as the initial operation processing result corresponding to the push service node.

[0205] In some embodiments, when the operation processing request includes a third operation processing request for querying an object attribute of a second account object, the at least one target node includes an object tag management node, an object operation management node, and a device attribute management node, and the operation parameter includes a second object identifier of the second account object; and the result acquisition submodule is specifically used to:

[0206] Based on the method implementation logic corresponding to the operation instruction identifier, generate a fourth query request for querying the object tag corresponding to the second account object, a fifth query request for querying the application operation log corresponding to the second account object, and a sixth query request for querying the device attributes of the device used by the second account object;

[0207] Sending a fourth query request to the object tag management node, obtaining the object tag returned by the object tag management node based on the fourth query request and the second object identifier as the initial operation processing result corresponding to the push service node;

[0208] Sending a fifth query request to the object operation management node, obtaining an application operation log returned by the object operation management node based on the fifth query request and the second object identifier as an initial operation processing result corresponding to the object operation management node;

[0209] A sixth query request is sent to the device attribute management node, and the device attribute returned by the device attribute management node based on the sixth query request and the second object identifier is obtained as an initial operation processing result corresponding to the device attribute management node.

[0210] In some embodiments, when the operation processing request includes a fourth operation processing request for stopping message push, at least one target node includes a push service node or a push management node, and the operation parameter includes a second push message identifier; the result acquisition submodule is specifically used to:

[0211] Generate a stop control request for stopping message push based on the method implementation logic corresponding to the operation instruction identifier;

[0212] Send a stop control request to the push management node, and obtain a push stop receipt returned by the push management node based on the stop control request and the second push message identifier as an initial operation processing result corresponding to the push management node;

[0213] A stop control request is sent to the push service node, and a push stop receipt returned by the push service node based on the stop control request and the second push message identifier is obtained as an initial operation processing result corresponding to the push service node.

[0214] In some embodiments, when the operation processing request includes a fifth operation processing request for intervening in message push, at least one target node includes a push service node, and the operation parameters include a third push message identifier and a target message intervention strategy; the result acquisition submodule is specifically used to:

[0215] Based on the method implementation logic corresponding to the operation instruction identifier, an intervention control request for intervention message push is generated; the intervention control request includes a target message intervention strategy;

[0216] An intervention control request is sent to the push service node, and a message intervention execution receipt is obtained, which is returned by the push service node based on the intervention control request, the third push message identifier and the target message intervention policy, as the initial operation processing result corresponding to the push service node; the message intervention execution receipt is at least used to characterize whether the push message corresponding to the third push message identifier is successfully intervened.

[0217] It should be noted that: when executing the push message processing device provided in the above embodiment, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the push message processing device provided in the above embodiment and the push message processing method embodiment belong to the same concept, and the push message processing device provided in the above embodiment and the push message processing method embodiment belong to the same concept. For technical details not described in detail in the above device embodiment, please refer to the method provided in any embodiment of the present application, and will not be repeated here.

[0218] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0219] An embodiment of the present application provides an electronic device, which may include a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement a method as described in any of the above method embodiments.

[0220] Further, Fig.121 is a schematic diagram of the hardware structure of an electronic device for implementing the method provided in the embodiment of the present application. Fig.12 The electronic device includes a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to implement the steps of any method in the above embodiments when executing the instructions stored in the memory.

[0221] The electronic device may be a terminal, a server or a similar computing device. For example, the electronic device is a server. Fig.12 It is a block diagram of an electronic device for processing push messages according to an exemplary embodiment. The electronic device 1000 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 1010 (the processor 1010 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 1030 for storing data, and one or more storage media 1020 (such as one or more mass storage devices) for storing application programs 1023 or data 1022. Among them, the memory 1030 and the storage medium 1020 can be short-term storage or persistent storage. The program stored in the storage medium 1020 may include one or more modules, each of which may include a series of instruction operations in the electronic device. Furthermore, the central processor 1010 can be configured to communicate with the storage medium 1020 and execute a series of instruction operations in the storage medium 1020 on the electronic device 1000.

[0222] The electronic device 1000 may also include one or more power supplies 1060, one or more wired or wireless network interfaces 1050, one or more input and output interfaces 1040, and / or one or more operating systems 1021, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc.

[0223] The input / output interface 1040 may be used to receive or send data via a network. The specific example of the network may include a wireless network provided by a communication provider of the electronic device 1000. In one example, the input / output interface 1040 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In an exemplary embodiment, the input / output interface 1040 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0224] It can be understood by those skilled in the art that Fig.12 The structure shown is only for illustration and does not limit the structure of the above electronic device. Fig.12 More or fewer components as shown, or with Fig.12 Different configurations are shown.

[0225] The embodiment of the present application also provides a computer-readable storage medium, wherein at least one instruction or at least one program is stored in the storage medium, and the at least one instruction or the at least one program is loaded and executed by a processor to implement any of the above methods. For example, the storage medium includes a memory of instructions, and the above instructions can be executed by a processor of the electronic device 1000 to complete the above method. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0226] The embodiment of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes any of the above-mentioned methods.

[0227] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0228] It should be noted that the above-mentioned sequence of the embodiments of the present application is for description only and does not represent the advantages and disadvantages of the embodiments. The above-mentioned specific embodiments of the present application are described. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0229] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and electronic device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0230] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0231] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A method for processing a push message, characterized in that: include: Get the operation processing request for the push message; The operation processing request is generated based on the operation message input in the chat interaction interface; Parsing the operation processing request to obtain an operation instruction identifier and an operation parameter corresponding to the operation instruction identifier; When the operation instruction identifier and the operation parameter respectively meet the preset operation triggering conditions, acquiring the operation processing result corresponding to the operation processing request from at least one target node related to the operation processing request in the push message link; The operation processing result is sent so that the operation processing result is displayed on the chat interaction interface.

2. The method according to claim 1, characterized in that The preset operation triggering condition includes a first operation triggering condition corresponding to the operation instruction identifier and a second operation triggering condition corresponding to the operation parameter; After obtaining the operation instruction identifier and the operation parameter corresponding to the operation instruction identifier, the method further includes: If there is a method implementation logic corresponding to the operation instruction identifier, determining that the operation instruction identifier satisfies the first operation triggering condition; If the operation parameter satisfies the legality condition, it is determined that the operation instruction identifier satisfies the second operation triggering condition.

3. The method according to claim 2, characterized in that After obtaining the operation instruction identifier and the operation parameter corresponding to the operation instruction identifier, the method further includes: If there is no method implementation logic corresponding to the operation instruction identifier, determining that the operation instruction identifier does not meet the first operation triggering condition; Sending instruction list auxiliary information for the operation instruction identifier, so that the instruction list auxiliary information is displayed on the chat interaction interface; or, If the operation parameter is empty or does not meet the legality condition, determining that the operation instruction identifier does not meet the second operation triggering condition; Send instruction parameter prompt information for the operation parameter so that the instruction parameter prompt information is displayed on the chat interaction interface.

4. The method according to claim 1, characterized in that: After obtaining the operation processing request for the push message, the method further includes: Obtaining the operation permission detection result of the request initiating object of the operation processing request; When the operation authority detection result indicates that the preset operation authority condition is not met, the operation authority prompt information is sent as the operation processing result corresponding to the operation processing request, so that the operation authority prompt information used to characterize insufficient operation authority is displayed on the chat interaction interface.

5. The method according to claim 1, characterized in that The method further comprises: In response to a method registration request for a push message, obtaining an operation method to be registered; If there is no registered method implementation logic for the method name corresponding to the operation method to be registered, register the operation method to be registered in the method registrar; If the method name corresponding to the operation method to be registered has a registered method implementation logic, a method registration failure message is sent.

6. The method according to any one of claims 1 to 5, characterized in that: The acquiring, from at least one target node related to the operation processing request in the push message link, an operation processing result corresponding to the operation processing request comprises: Based on the operation processing request, determining at least one target node related to the operation processing request from the push message link; Acquire the initial operation processing results returned by each of the target nodes; the initial operation processing results are determined based on the method implementation logic corresponding to the operation instruction identifier and the operation parameters; Each of the initial operation processing results is encapsulated to obtain an operation processing result corresponding to the operation processing request.

7. The method according to claim 6, characterized in that In a case where the operation processing request includes a first operation processing request for querying a push message attribute, the at least one target node includes a push service node and a push management node, and the operation parameter includes a first push message identifier; The obtaining of the initial operation processing results returned by each of the target nodes includes: Based on the method implementation logic corresponding to the operation instruction identifier, generate a first query request for querying the push status and a second query request for querying the push parameter settings; Sending the first query request to the push service node, and acquiring a push status returned by the push service node based on the first query request and the first push message identifier as an initial operation processing result corresponding to the push service node; The second query request is sent to the push management node, and the push parameter setting returned by the push management node based on the second query request and the first push message identifier is obtained as an initial operation processing result corresponding to the push management node.

8. The method according to claim 6, characterized in that In a case where the operation processing request includes a second operation processing request for querying a push result of a push message for a first account object, the at least one target node includes a push service node, and the operation parameter includes a first object identifier of the first account object; The obtaining of the initial operation processing results returned by each of the target nodes includes: Based on the method implementation logic corresponding to the operation instruction identifier, generate a third query request for querying the push result of the push message for the first account object; Sending the third query request to the push service node; In a case where the operation parameter also includes a push message identifier to be queried, obtaining a push result returned by the push service node based on the third query request, the first object identifier and the push message identifier to be queried as an initial operation processing result corresponding to the push service node; When the operation parameters do not include the push message identifier to be queried, the push result of the push message of the day returned by the push service node based on the third query request and the first object identifier is obtained as the initial operation processing result corresponding to the push service node.

9. The method according to claim 6, characterized in that In a case where the operation processing request includes a third operation processing request for querying an object attribute of a second account object, the at least one target node includes an object tag management node, an object operation management node, and a device attribute management node, and the operation parameter includes a second object identifier of the second account object; The obtaining of the initial operation processing results returned by each of the target nodes includes: Based on the method implementation logic corresponding to the operation instruction identifier, generate a fourth query request for querying the object tag corresponding to the second account object, a fifth query request for querying the application operation log corresponding to the second account object, and a sixth query request for querying the device attributes of the device used by the second account object; Sending the fourth query request to the object tag management node, and obtaining the object tag returned by the object tag management node based on the fourth query request and the second object identifier as the initial operation processing result corresponding to the push service node; Sending the fifth query request to the object operation management node, and obtaining the application operation log returned by the object operation management node based on the fifth query request and the second object identifier as the initial operation processing result corresponding to the object operation management node; The sixth query request is sent to the device attribute management node, and the device attribute returned by the device attribute management node based on the sixth query request and the second object identifier is obtained as an initial operation processing result corresponding to the device attribute management node.

10. The method according to claim 6, characterized in that In a case where the operation processing request includes a fourth operation processing request for stopping message push, the at least one target node includes a push service node or a push management node, and the operation parameter includes a second push message identifier; The obtaining of the initial operation processing results returned by each of the target nodes includes: Generate a stop control request for stopping message push based on the method implementation logic corresponding to the operation instruction identifier; Sending the stop control request to the push management node, and obtaining a push stop receipt returned by the push management node based on the stop control request and the second push message identifier as an initial operation processing result corresponding to the push management node; The stop control request is sent to the push service node, and a push stop receipt returned by the push service node based on the stop control request and the second push message identifier is obtained as an initial operation processing result corresponding to the push service node.

11. The method according to claim 6, characterized in that In a case where the operation processing request includes a fifth operation processing request for intervening in message push, the at least one target node includes a push service node, and the operation parameters include a third push message identifier and a target message intervention strategy; The obtaining of the initial operation processing results returned by each of the target nodes includes: Based on the method implementation logic corresponding to the operation instruction identifier, an intervention control request for intervening in message push is generated; the intervention control request includes the target message intervention strategy; Send the intervention control request to the push service node, and obtain the message intervention execution receipt returned by the push service node based on the intervention control request, the third push message identifier and the target message intervention policy as the initial operation processing result corresponding to the push service node; the message intervention execution receipt is at least used to characterize whether the push message corresponding to the third push message identifier is successfully intervened.

12. A push message processing device, characterized in that: The device comprises: A request acquisition module, used to acquire an operation processing request for a push message; the operation processing request is generated based on an operation message input in the chat interaction interface; A parsing module, used for parsing the operation processing request, obtaining an operation instruction identifier and an operation parameter corresponding to the operation instruction identifier; A result acquisition module, configured to acquire an operation processing result corresponding to the operation processing request from at least one target node related to the operation processing request in a push message link when the operation instruction identifier and the operation parameter respectively meet preset operation triggering conditions; The sending module is used to send the operation processing result so that the operation processing result can be displayed on the chat interaction interface.

13. A computer-readable storage medium, characterized in that: The storage medium stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the push message processing method according to any one of claims 1-11.

Images