Message interaction method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a message interaction method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: acquiring a target push message, and identifying a message scene of the target push message; performing rule searching processing based on the message scene, and determining a message pushing crowd rule corresponding to the message scene; performing target identification processing according to the message push crowd rule, and determining a target terminal of a target push message; and distributing the target push message to the target terminal in an event stream mode. By customizing the message scene of the message and setting the corresponding message pushing crowd rule, when interaction processing of message distribution needs to be carried out, the target pushing message can be distributed to the target terminal in combination with the message scene, so that mutual communication between the terminals is effectively realized, effective transmission of the message is ensured, and the user experience is improved. The information interaction efficiency and accuracy are improved, and the safety of a power grid system is ensured.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a message interaction method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the development of digital power grid operation, the power system continues to expand. Under the condition of safe power grid operation, the scope of dispatching business operations continues to expand, and the content involved in power grid business has also increased dramatically. With the continuous migration of the functions of the current system to mobile terminals, in order to facilitate the use of system functions and better solve the time, space, and regional limitations of the system functions used by dispatching operations, it is necessary to realize effective information interaction processing between the client and the mobile terminal.

[0003] At present, third-party message push vendors are generally used for information interaction between clients and mobile terminals. However, the traditional message notification mechanism cannot realize message customization, resulting in a large number of personalized scenarios that cannot be communicated, and the messages of clients and mobile terminals cannot be managed uniformly. In addition, the messages of clients and mobile terminals cannot communicate in real time, resulting in inconsistent information obtained by the users of both, which reduces the ability of the district bureau operation and maintenance personnel and the customer service center to regulate the line current, and there are abnormal or erroneous operations. This brings huge hidden dangers to the lines of the entire power grid and affects the normal operation of the power grid dispatching. Summary of the invention

[0004] Based on this, it is necessary to provide a message interaction method, device, computer equipment, computer-readable storage medium and computer program product that can ensure the efficiency and accuracy of information interaction and thus ensure the security of the power grid system in response to the above technical problems.

[0005] In a first aspect, the present application provides a message interaction method, comprising:

[0006] Obtaining a target push message, and identifying a message scenario of the target push message;

[0007] Perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario;

[0008] Performing target identification processing according to the message push crowd rule to determine the target terminal of the target push message;

[0009] The target push message is distributed to the target terminal in an event stream manner.

[0010] In one embodiment, the method further comprises:

[0011] Get the message scene division request;

[0012] Based on the message scene division request, feeding back a rule setting interface for each message scene divided by the message scene division request;

[0013] When the message push crowd rule fed back based on the rule setting interface is received, the message scenario and the message push crowd rule are associated and stored in a rule database.

[0014] In one embodiment, the performing rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario includes:

[0015] A rule search process is performed in a rule database based on the message scenario, and if a message push crowd rule corresponding to the message scenario is not found, the message push crowd rule corresponding to the message scenario is determined to be a message distribution algorithm.

[0016] In one embodiment, performing target identification processing according to the message push crowd rule to determine the target terminal of the target push message includes:

[0017] In the case where the message push crowd rule is a message distribution algorithm, an event claiming client of a scene event corresponding to the target push message is identified, and the event claiming client is determined as a target terminal of the target push message.

[0018] In one embodiment, the method further comprises:

[0019] Obtaining a service processing request of the target terminal based on the target push message feedback;

[0020] Perform business scenario search processing based on the business processing request to obtain a business processing interface;

[0021] Feedback the service processing interface to the target terminal.

[0022] In one of the embodiments, the target terminal includes a mobile client and a scheduling client;

[0023] The method further comprises:

[0024] Obtain the business event receipt code of the mobile client;

[0025] Generate an event receipt message based on the business event receipt code, and send the event receipt message to the scheduling client;

[0026] When receiving an event confirmation message fed back by the scheduling client based on the event receipt message, the event confirmation message is forwarded to the mobile client.

[0027] In a second aspect, the present application also provides a message interaction device, including:

[0028] A message acquisition module, used to acquire a target push message and identify a message scenario of the target push message;

[0029] A rule search module is used to perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario;

[0030] A target identification module, used to perform target identification processing according to the message push crowd rule and determine the target terminal of the target push message;

[0031] The message distribution module is used to distribute the target push message to the target terminal in an event stream manner.

[0032] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0033] Obtaining a target push message, and identifying a message scenario of the target push message;

[0034] Perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario;

[0035] Performing target identification processing according to the message push crowd rule to determine the target terminal of the target push message;

[0036] The target push message is distributed to the target terminal in an event stream manner.

[0037] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0038] Obtaining a target push message, and identifying a message scenario of the target push message;

[0039] Perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario;

[0040] Performing target identification processing according to the message push crowd rule to determine the target terminal of the target push message;

[0041] The target push message is distributed to the target terminal in an event stream manner.

[0042] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0043] Obtaining a target push message, and identifying a message scenario of the target push message;

[0044] Perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario;

[0045] Performing target identification processing according to the message push crowd rule to determine the target terminal of the target push message;

[0046] The target push message is distributed to the target terminal in an event stream manner.

[0047] The above-mentioned message interaction method, apparatus, computer equipment, computer-readable storage medium and computer program product obtain the target push message and identify the message scenario of the target push message; perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario; perform target identification processing according to the message push crowd rule to determine the target terminal of the target push message; and distribute the target push message to the target terminal in an event stream manner. This application customizes the message scenario of the message and sets the corresponding message push crowd rules. When interactive processing of message distribution is required, the target push message can be distributed to the target terminal in combination with the message scenario, thereby effectively realizing mutual communication between terminals, ensuring the effective transmission of messages, improving the efficiency and accuracy of information interaction, and ensuring the security of the power grid system. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0049] FIG1 is an application environment diagram of a message interaction method in one embodiment;

[0050] FIG2 is a schematic diagram of a flow chart of a message interaction method in one embodiment;

[0051] FIG3 is a schematic diagram of a flow chart of scene division and rule storage steps in one embodiment;

[0052] FIG4 is a schematic diagram of an interactive scene of a field operation process in one embodiment;

[0053] FIG5 is a structural block diagram of a message interaction device in one embodiment;

[0054] FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0056] The message interaction method provided in the embodiment of the present application can be applied to the application environment shown in Figure 1. Among them, multiple mobile terminals 102 and multiple client terminals 104 communicate with the communication server 106 of the mobile interaction center through the network respectively. The communication server 106 is used to realize the message interaction processing between the mobile terminal 102 and the client terminal 104. In addition, the communication server 106 can also communicate with various types of devices in the system. The data storage system can store the data that the communication server 106 needs to process. The data storage system can be integrated on the communication server 106, or it can be placed on the cloud or other network servers. When the client needs to push a message to other clients or mobile terminals, a corresponding target push message can be generated. And the target push message is submitted to the communication server 106, and the communication server 106 obtains the target push message and identifies the message scenario of the target push message; based on the message scenario, the rule search processing is performed to determine the message push crowd rule corresponding to the message scenario; according to the message push crowd rule, the target identification processing is performed to determine the target terminal of the target push message; the target push message is distributed to the target terminal in an event stream manner. The communication server 106 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0057] In an exemplary embodiment, as shown in FIG2 , a message interaction method is provided, which is described by taking the method applied to the communication server 106 in FIG1 as an example, and includes the following steps 201 to 207. Among them:

[0058] Step 201: Obtain a target push message and identify a message scenario of the target push message.

[0059] Among them, the target push message refers to the message that needs to be pushed to the corresponding terminal. The target push message can be generated by the mobile terminal 102 or the client terminal 104 in the system, or it can be generated by the device in the system. For example, in an emergency such as a failure of the device in the system, a corresponding target push message can be generated to inform other terminals in the system. The message scene is pre-set by the administrator, such as ordinary messages, log messages, verification messages, operation messages, etc.

[0060] Exemplarily, when the staff of the mobile terminal 102 or the client terminal 104 need to interact with information to synchronize the latest message to other terminals, a target push message can be sent to the communication server 106. After receiving the target push message, the communication server 106 will first identify the message scenario of the target push message based on the identifier carried by the target push message, the source of the target message, or the type of the target message. In one embodiment, the present application is applied to the message interaction of the power grid system. At this time, the dispatcher responsible for communication management can define the message scenario, such as ordinary messages, log-type messages, verification messages, operation messages, etc. Then, according to these message scenarios, the message interaction is carried out, wherein for each message scenario, the ordinary message is mainly based on notification, prompting the user to inform the user of a certain message content, such as generating a fault event prompt, a certain line load rate has reached 80% prompt, a verification code prompt, etc. The log type message refers to the on-site personnel performing the dispatching operation, generating a completion operation message, notifying the dispatcher to confirm the operation status and generate a log, such as a three-remote switch fault confirmation message, a fault event receipt message, a fault handling recovery message, etc. Verification messages are used to notify the dispatcher to verify the line of the ring network diagram. After opening the message, the ring network diagram will be automatically opened, such as verifying the switch message, disconnecting the reclosing switch message, closing the reclosing switch message, etc. Operational messages are used when the dispatcher receives the message and opens the message to perform dispatch operations. Work can be assigned, operation tickets can be prepared, operation tickets can be reviewed, and operation tickets can be executed, such as switch application messages, operation ticket completion messages, and new work order messages.

[0061] Step 203: Perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario.

[0062] Exemplarily, the message push crowd rule refers to the rule used to determine the terminal to which the target push message needs to be pushed. The message push crowd rule can be divided into custom notification rules and message distribution algorithms. Custom notification rules are set by staff based on specific work needs. They can be user-specified notification persons, or notification group members, or definition of regular matching notification terminal accounts, etc. The message distribution algorithm is the default distribution rule when no custom push rules are set. Different scenarios can correspond to different message push crowd rules. After identifying the message scenario, the message push crowd rules can be used.

[0063] Step 205: Perform target identification processing according to the message push crowd rule to determine the target terminal of the target push message.

[0064] Exemplarily, after finding the message push crowd rule, target identification processing can be performed based on the message push crowd rule. The target identification processing is mainly used to determine the push target pointed to by the current target push message. If the message push crowd rule is a case where the user specifies the person to be notified, the identifier of the target terminal is directly extracted to determine the target terminal. If the message push crowd rule is a case where the group members are notified, the group identifier is directly extracted, and then the target terminal of the group pointed to by the group representation is determined. When it is determined that the message push crowd rule is a message distribution algorithm, the target push message can be sent to the claimant of the event to which the target push message belongs.

[0065] Step 207: Distribute the target push message to the target terminal in an event stream manner.

[0066] Among them, Server-Sent Events (SSE) is a technology based on HTTP that continuously sends data from the server to the client in the form of a stream. It is easy to develop and is almost the same as traditional http development. Client development is simple and has standard support.

[0067] Exemplarily, in this application, the distribution and processing of the target push message is specifically implemented by means of an event stream. With the support of the event stream, the communication server 106 can uniformly manage the message after receiving the message, and distribute the message in a timely manner according to the push crowd rules or message distribution algorithm (MDA) defined in advance by the user to ensure the timeliness of each message. The event stream allows the communication server 106 to push data to each terminal in real time. Compared with traditional polling or long polling technology, the event stream has lower latency, higher efficiency and lower resource consumption. In addition, the event stream can also automatically reconnect by setting the retry field to ensure the stability of the connection.

[0068] The above-mentioned message interaction method obtains the target push message and identifies the message scenario of the target push message; performs rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario; performs target identification processing according to the message push crowd rule to determine the target terminal of the target push message; and distributes the target push message to the target terminal in an event stream manner. This application customizes the message scenario of the message and sets the corresponding message push crowd rules. When interactive processing of message distribution is required, the target push message can be distributed to the target terminal in combination with the message scenario, thereby effectively realizing mutual communication between terminals, ensuring the effective transmission of messages, improving the efficiency and accuracy of information interaction, and ensuring the safety of the power grid system.

[0069] In an exemplary embodiment, as shown in FIG3 , the method further includes:

[0070] Step 302: Obtain a message scene division request.

[0071] Step 304: Based on the message scene division request, a rule setting interface for each message scene divided by the message scene division request is fed back.

[0072] Step 306: upon receiving the message push crowd rule fed back based on the rule setting interface, the message scenario and the message push crowd rule are associated and stored in the rule database.

[0073] The message scenario division request is a request for staff to create information scenarios and message push crowd rules. In the initial stage of the plan or when developing new businesses, staff may need to set corresponding message push crowd rules for new business scenarios. At this time, you can submit a message scenario division request to build a new message scenario and set the message push crowd rules corresponding to the message scenario.

[0074] Exemplarily, in the initial stage of the scheme or the development of new business, the staff needs to complete the division of message scenes and the rule setting of message scenes first. First, the staff can submit the corresponding message scene division request to the back-end communication server equipped with the message interaction method of the present application through the terminal. The back-end communication server receives the message scene division request, determines the various scenes divided by the message scene division request, such as ordinary messages, log messages, verification messages, operation messages and other scenes, and then feeds back the rule setting interface of each message scene divided by the message scene division request to the terminal where the staff is located. The staff can fill in the corresponding message push crowd rules under these scenes at the terminal, and the unfilled scenes use the message distribution algorithm as the message push crowd rule by default. After the rule setting interface is filled in, it will be fed back to the back-end communication server, and the back-end communication server will associate the message scene and the message push crowd rule and store it in the rule database, so as to efficiently search and process the rules in the future. In this embodiment, the division of message scenes and the setting of message push crowd rules are realized based on the message scene division request, which can effectively ensure the recognition accuracy of the target terminal corresponding to the target push message, thereby ensuring the accuracy of the target push message distribution during the message distribution process.

[0075] In an exemplary embodiment, step 203 includes: performing rule search processing in a rule database based on a message scenario, and if a message push crowd rule corresponding to the message scenario is not found, determining that the message push crowd rule corresponding to the message scenario is a message distribution algorithm.

[0076] Exemplarily, the present application may select a message distribution algorithm as the default message push crowd rule. If the message push crowd rule corresponding to the message scenario is not found, the message push crowd rule corresponding to the message scenario is directly determined to be a message distribution algorithm (MDA). For the message distribution algorithm, when the scene event is generated, the first message notification is to the event creator. When the event is claimed by other people, all messages of this event are pushed only to the person who claimed the event (other people can handle the event). When the message push crowd rule is the message distribution algorithm, the event claiming client of the scene event corresponding to the target push message is identified, and the event claiming client is determined as the target terminal of the target push message. In a specific embodiment, the present application is specifically applied to the message distribution processing of the distribution network business. The dispatching shift of the distribution network business is divided into three shifts: morning, middle and evening. If the message is still not processed when the shift changes, and no one has handled the event on this shift, then under the message distribution algorithm, the newly generated message notification is sent by default to the dispatcher who last handled the event on the previous shift. When someone handles the message on this shift, the subsequent new messages of this event are distributed by default to the dispatcher who first handled the event on this shift. In this embodiment, the message distribution process is implemented in a default state according to the message distribution algorithm, which can effectively ensure the efficiency and accuracy of the message distribution process.

[0077] In an exemplary embodiment, the method further includes: obtaining a business processing request from the target terminal based on the target push message feedback; performing business scenario search processing based on the business processing request to obtain a business processing interface; and feeding back the business processing interface to the target terminal.

[0078] Exemplarily, the present application can also realize the message scene business operation processing through the target push message. When the user receives the target push message, the business processing request can be directly fed back. Then the server searches and processes through the business scene to obtain the business processing interface, and feeds back the business processing interface to the target terminal based on the target push message, thereby opening the processing entrance of the message personalized scene, so that the user can directly perform the operation processing. For example, after the switch application operation message is opened, the dispatcher can directly operate the draft ticket business, and after the switch verification message is opened, the dispatcher can modify the ring network diagram switch state, etc. Therefore, different businesses can be processed according to the messages of different scenarios, such as the three-remote switch fault confirmation message, the fault event receipt message, and the fault processing recovery message can generate a dispatch confirmation log, and the switch verification message, the disconnection reclosing message, and the closing reclosing message can modify the power grid line diagram information; the switch application message can open the ring network diagram to operate the ticket drafting, and the operation ticket completion message can open the dispatching function to dispatch the work order, so that the on-site personnel can perform the operation processing. In this embodiment, the business processing interface is directly searched and fed back through the business processing request, so as to effectively speed up the efficiency of related businesses based on message interaction processing.

[0079] In an exemplary embodiment, the target terminal includes a mobile client and a scheduling client. The method further includes: obtaining a service event receipt code of the mobile client; generating an event receipt message based on the service event receipt code, and sending the event receipt message to the scheduling client; and forwarding the event confirmation message to the mobile client when receiving an event confirmation message fed back by the scheduling client based on the event receipt message.

[0080] Exemplarily, the mobile client and the dispatch client specifically refer to the terminal equipment in the field operation. The mobile client is operated by the field operation personnel, and the dispatch client is operated by the remote dispatcher. The present application can be specifically used to realize the message interaction of the field operation scene. It is necessary to first send the event reception verification code to the mobile client of the field personnel, and the field personnel receive the verification code by signing the event; after receiving the notification of the newly added fault event, the event is signed and the fault event is processed. After signing on site, the business event receipt code is sent to the dispatch client, and the dispatcher of the dispatch client can confirm it. After the dispatcher confirms, the work can be carried out on site. In addition, after the event processing is confirmed, the information interaction between the mobile client and the dispatch client in the event execution process can also be realized through the operation ticket command notification. After receiving the command notification, the field personnel execute the operation ticket in the interactive center of the mobile client. For each step of the operation ticket, a notification message is sent to the dispatch client to update the progress of the operation ticket execution step. In a specific embodiment, the dispatch client is implemented by a PC client, and the message interaction method of the present application is implemented by an MSC (Mobile Switching Center). At this time, the information interaction flow chart of the field operation process can be shown in Figure 4. In this embodiment, the interaction between the dispatch client and the mobile terminal is realized. The message interaction between the dispatch client and the mobile client can be managed in an orderly manner, the timeliness of the message can be guaranteed, and the customer can quickly perform the dispatch operation according to the message of the customized scenario. The dispatch personnel's real-time control over the dispatch operation information is improved. When applied to the power grid, the monitoring capability of all operating lines of the power grid can be strengthened, thereby improving the safety of the power grid operation.

[0081] In one embodiment, the message interaction method of the present application includes: obtaining a message scene division request; based on the message scene division request, feeding back a rule setting interface for each message scene divided by the message scene division request; in the case of receiving a message push crowd rule fed back based on the rule setting interface, associating the message scene with the message push crowd rule and storing it in a rule database. Obtaining a target push message and identifying the message scene of the target push message; performing rule search processing based on the message scene to determine the message push crowd rule corresponding to the message scene. In the case where the message push crowd rule corresponding to the message scene is not found, determining that the message push crowd rule corresponding to the message scene is a message distribution algorithm, and in the case where the message push crowd rule is a message distribution algorithm, identifying the event claiming client of the scene event corresponding to the target push message, and determining the event claiming client as the target terminal of the target push message. Performing target identification processing according to the message push crowd rule to determine the target terminal of the target push message; distributing the target push message to the target terminal in an event stream manner. Obtaining a business processing request fed back by the target terminal based on the target push message; performing business scene search processing based on the business processing request to obtain a business processing interface; and feeding back the business processing interface to the target terminal.

[0082] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0083] Based on the same inventive concept, the embodiment of the present application also provides a message interaction device for implementing the message interaction method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more message interaction device embodiments provided below can refer to the limitations on the message interaction method above, and will not be repeated here.

[0084] In an exemplary embodiment, as shown in FIG5 , a message interaction device is provided, including:

[0085] The message acquisition module 502 is used to acquire a target push message and identify a message scenario of the target push message.

[0086] The rule search module 504 is used to perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario.

[0087] The target identification module 506 is used to perform target identification processing according to the message push crowd rule and determine the target terminal of the target push message.

[0088] The message distribution module 508 is used to distribute the target push message to the target terminal in an event stream manner.

[0089] In one embodiment, it also includes a rule setting module, which is used to: obtain a message scene division request; based on the message scene division request, feedback a rule setting interface for each message scene divided by the message scene division request; when receiving a message push crowd rule based on the feedback of the rule setting interface, the message scene and the message push crowd rule are associated and stored in the rule database.

[0090] In one embodiment, the rule search module 504 is specifically used to: perform rule search processing in the rule database based on the message scenario, and if the message push crowd rule corresponding to the message scenario is not found, determine that the message push crowd rule corresponding to the message scenario is the message distribution algorithm.

[0091] In one embodiment, the target identification module 506 is specifically used to: when the message push crowd rule is a message distribution algorithm, identify the event claiming client of the scene event corresponding to the target push message, and determine the event claiming client as the target terminal of the target push message.

[0092] In one embodiment, it also includes a business processing module, which is used to: obtain a business processing request from the target terminal based on the target push message feedback; perform business scenario search processing based on the business processing request to obtain a business processing interface; and feed back the business processing interface to the target terminal.

[0093] In one embodiment, the target terminal includes a mobile client and a scheduling client; the device also includes a scheduling authentication module, which is used to: obtain a business event receipt code from the mobile client; generate an event receipt message based on the business event receipt code, and send the event receipt message to the scheduling client; and forward the event confirmation message to the mobile client upon receiving an event confirmation message from the scheduling client based on the event receipt message feedback.

[0094] Each module in the above message interaction device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0095] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG6. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data related to message interaction. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a message interaction method is implemented.

[0096] Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0097] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0098] In one embodiment, a computer-readable storage medium is provided, storing a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0099] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in the above-mentioned method embodiments.

[0100] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0101] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method 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 the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0102] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0103] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A message interaction method, characterized in that: The method comprises: Obtaining a target push message, and identifying a message scenario of the target push message; Perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario; Performing target identification processing according to the message push crowd rule to determine the target terminal of the target push message; The target push message is distributed to the target terminal in an event stream manner.

2. The method according to claim 1, characterized in that: The method further comprises: Get the message scene division request; Based on the message scene division request, feeding back a rule setting interface for each message scene divided by the message scene division request; When the message push crowd rule fed back based on the rule setting interface is received, the message scenario and the message push crowd rule are associated and stored in a rule database.

3. The method according to claim 2, characterized in that The performing rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario includes: A rule search process is performed in a rule database based on the message scenario, and if a message push crowd rule corresponding to the message scenario is not found, the message push crowd rule corresponding to the message scenario is determined to be a message distribution algorithm.

4. The method according to claim 3, characterized in that: The performing target identification processing according to the message push crowd rule to determine the target terminal of the target push message includes: In the case where the message push crowd rule is a message distribution algorithm, an event claiming client of a scene event corresponding to the target push message is identified, and the event claiming client is determined as a target terminal of the target push message.

5. The method according to claim 1, characterized in that The method further comprises: Obtaining a service processing request of the target terminal based on the target push message feedback; Perform business scenario search processing based on the business processing request to obtain a business processing interface; Feedback the service processing interface to the target terminal.

6. The method according to any one of claims 1 to 5, characterized in that: The target terminal includes a mobile client and a scheduling client; The method further comprises: Obtain the business event receipt code of the mobile client; Generate an event receipt message based on the business event receipt code, and send the event receipt message to the scheduling client; When receiving an event confirmation message fed back by the scheduling client based on the event receipt message, the event confirmation message is forwarded to the mobile client.

7. A message interaction device, characterized in that: The device comprises: A message acquisition module, used to acquire a target push message and identify a message scenario of the target push message; A rule search module is used to perform rule search processing based on the message scenario to determine the message push crowd rule corresponding to the message scenario; A target identification module, used to perform target identification processing according to the message push crowd rule and determine the target terminal of the target push message; The message distribution module is used to distribute the target push message to the target terminal in an event stream manner.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images