CN114721740A

CN114721740A - Message triggering method, device, equipment and storage medium

Info

Publication number: CN114721740A
Application number: CN202210359337.6A
Authority: CN
Inventors: 姚聪聪
Original assignee: Ping An International Financial Leasing Co Ltd
Current assignee: Ping An International Financial Leasing Co Ltd
Priority date: 2022-04-06
Filing date: 2022-04-06
Publication date: 2022-07-08

Abstract

The invention discloses a message triggering method, a message triggering device, message triggering equipment and a storage medium. The method is applied to a message service platform, the message service platform integrates a database Redis and a message queue RabbitMQ based on a SpringBoot framework, and the method comprises the following steps: responding to the message configuration operation of the calling application program APP on the visual configuration interface, and generating a message template; determining a receiver APP by adopting a Redis overdue monitoring mechanism, and triggering the sending of a push message; and generating a push message matched with the message template by using a producer and consumer mode of the RabbitMQ, and sending the push message to the receiver APP. According to the technical scheme of the embodiment of the invention, the message service platform with the unified message configuration function and the message trigger function is arranged, so that the use complexity of the APP message trigger function is reduced.

Description

Message triggering method, device, equipment and storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for triggering a message.

Background

With the continuous development of various Applications (APPs), each APP has a set of its own message system.

When a frame used by a certain APP does not support a page to be jumped by a message, it is possible to jump to a specified local page which already exists. If upgrade iteration is encountered and the APP is not upgraded to the latest version, the push message may not be received due to version mismatch, or after the push message is received, the user may not jump to the local page normally due to the fact that the specified parameter is not found, so that bad experience may be brought to the user.

Moreover, the existing message mechanism is complex, a developer needs to know the mechanism in each message sufficiently, and the message can be used through a series of processes such as investigation, account application, logic implementation and the like, so that the development cost is high, and the expandability is poor.

Disclosure of Invention

The invention provides a message triggering method, a message triggering device, message triggering equipment and a storage medium, wherein the complexity of the application of an APP message triggering function is reduced by arranging a message service platform with a unified message configuration function and a message triggering function.

According to one aspect of the invention, a message triggering method is provided, which is applied to a message service platform, wherein the message service platform integrates a database Redis and a message queue RabbitMQ based on a Spring Boot framework, and the method comprises the following steps:

responding to the message configuration operation of the calling party application program APP on the visual configuration interface, and generating a message template;

determining a receiver APP by adopting a Redis overdue monitoring mechanism, and triggering the sending of a push message;

and generating a push message matched with the message template by using a producer and consumer mode of the RabbitMQ, and sending the push message to the receiver APP.

Optionally, before generating the message template in response to the message configuration operation of the calling party APP on the visual configuration interface, the method further includes:

responding to a key application request of a calling party APP, and feeding back a pair of public key and private key to the calling party APP; and the public key and the private key are used for accessing the calling party APP to the message service platform for function calling.

Optionally, the message template includes: template name, message type, jump protocol, jump parameter and message content; the jump protocol comprises: scheme jump protocol based on Flutter framework.

Optionally, after generating a push message matched with the message template using a producer and consumer model of a RabbitMQ, and sending the push message to the recipient APP, the method further includes: storing the detailed content of each sent push message into Redis;

and responding to the troubleshooting request, and acquiring the detailed content of the push message stored in the Redis to perform message analysis and alarm.

Optionally, the method further includes: if the message type configuration request is obtained, encoding to realize a new message type corresponding to the message type configuration request;

and when the calling party APP configures the message template on the visual configuration interface, providing the new message type as a selectable item for the calling party APP.

Optionally, determining the recipient APP by using a Redis expiration monitoring mechanism includes:

determining the upper limit of the monitoring time of the Redis overdue monitoring mechanism, and monitoring the message event corresponding to the message template;

and when a target message event of which the monitoring time reaches the upper limit of the monitoring time is detected, taking the APP corresponding to the target message event as an APP of a receiver.

Optionally, after receiving the push message, the recipient APP performs Scheme jump protocol analysis on the push message, determines a jump parameter and a page to be jumped, and jumps to the page to be jumped from a display page of the push message according to the jump parameter.

According to another aspect of the present invention, there is provided a message trigger device applied to a message service platform, where the message service platform integrates a database Redis and a message queue RabbitMQ based on a Spring Boot framework, and the message trigger device includes:

the configuration module is used for responding to the message configuration operation of the calling party APP on the visual configuration interface and generating a message template;

the message triggering module is used for determining an APP of a receiver by adopting a Redis overdue monitoring mechanism and triggering the sending of the push message;

and the message pushing module is used for generating a pushing message matched with the message template by using a producer and consumer mode of the RabbitMQ, and sending the pushing message to the receiver APP.

According to another aspect of the present invention, there is provided an electronic apparatus including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the message triggering method of any of the embodiments of the present invention.

According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement a message triggering method according to any one of the embodiments of the present invention when the computer instructions are executed.

The technical scheme of the embodiment of the invention is applied to a message service platform, the message service platform integrates a database Redis and a message queue RabbitMQ based on a Spring Boot framework, and the message service platform generates a message template by responding to the message configuration operation of a calling party application program APP on a visual configuration interface; determining a receiver APP by adopting a Redis overdue monitoring mechanism, and triggering the sending of a push message; the method comprises the steps of generating a push message matched with a message template by using a producer and consumer mode of a RabbitMQ, sending the push message to a receiver APP, solving the problems of high development cost and poor expandability of the APP trigger message, and obtaining the beneficial effect of reducing the complexity of the APP message trigger function by setting a message service platform with a unified message configuration function and a message trigger function.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a flowchart of a message triggering method according to an embodiment of the present invention;

FIG. 2 is a screenshot of a visualization configuration interface suitable for use in accordance with an embodiment of the present invention;

fig. 3 is a schematic structural diagram of a message trigger apparatus according to a second embodiment of the present invention;

fig. 4 is a schematic structural diagram of an electronic device implementing the message triggering method according to the embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "caller APP", "receiver APP", and the like in the description and claims of the present invention and the above drawings are used for distinguishing similar objects and are not necessarily used for describing a specific order or sequence. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example one

Fig. 1 is a flowchart of a message triggering method according to an embodiment of the present invention, where this embodiment is applicable to a case where a calling party APP accessing a message service platform implements message triggering, and the method may be executed by a message triggering apparatus applied to the message service platform, where the message triggering apparatus may be implemented in a form of hardware and/or software, and the message triggering apparatus may be configured in an electronic device. As shown in fig. 1, the method includes:

and S110, responding to the message configuration operation of the calling party APP on the visual configuration interface, and generating a message template.

The message service platform integrates a database Redis and a message queue RabbitMQ based on a Spring Boot framework. The Spring Boot framework integrates functions of an embedded Web server, system monitoring and the like, and is used for quickly constructing enterprises and application programs. Redis is a key-value pair storage database that contains a variety of data structures, supports distributed, memory-based operations. The RabbitMQ is Message-oriented Message middleware implemented based on Advanced Message Queue (AMQP) protocol.

The calling party APP is an APP which is accessed to the message service platform, actively calls a message configuration function of the message service platform to configure the message template and configures the message triggering condition. Correspondingly, the APP that receives the specified message sent by the message service platform may be referred to as a recipient APP. The specified message may be a message generated according to a configuration template of the caller APP.

In this embodiment, the visual configuration interface provided by the message service platform is used as a uniform entry for configuring the message template, so that all APPs accessing the message service platform can configure the message template on the visual configuration interface as required. As shown in fig. 2, the message template includes data items required for generating a message to be pushed. Optionally, the message template includes: template name, message type, jump protocol, jump parameter and message content; the jump protocol comprises the following steps: scheme jump protocol based on Flutter framework.

The message type may include types such as push notification bar message, dynamic message, etc., the jump protocol may include javascript protocol, Intent protocol, Scheme jump protocol, etc., and the jump parameter may be an identifier of a page to be jumped, a page address, etc. The Flutter is a mobile UI framework, can use one code to quickly construct a high-quality native user interface on iOS and Android, and realizes cross-device and cross-platform high-quality user experience by means of a portable graphic accelerated rendering engine and a high-performance local ARM code. According to the embodiment, through the Scheme jump protocol based on the Flutter frame, complex page jump and parameter transmission can be supported on the iOS and the Android, and parameter transmission loading of a new h5 page is achieved, the fact that the receiver APP can normally achieve page jump is guaranteed, and the problem that the page cannot be jumped is avoided.

In this embodiment, through the visual configuration interface that the message service platform provided, realize that calling party APP waits the message body of propelling movement message in unified entry one-key configuration, calling party APP need not pay close attention to the trigger mechanism and the process of message, only need according to the message template of configuration, appoint the APP of receiving the message, the ID of the customer end of receiving the message, other all are realized by the message service platform, great reduction the complexity that the message function used, practiced thrift the time that calling party APP carried out processes such as investigation, application, development.

Optionally, before generating the message template in response to the message configuration operation of the calling party APP on the visual configuration interface, the method may further include: responding to a key application request of a calling party APP, and feeding back a pair of public key and private key to the calling party APP; and the public key and the private key are used for calling the APP of the calling party to access the message service platform for function calling.

In this embodiment, in order to ensure data security, the message service platform allocates an access right to the APP that is successfully registered on the platform, so that when the message service platform receives an access request of the APP, whether the APP is allowed to access can be determined by verifying whether the APP has the access right. The message service platform can provide different keys for different APPs, so that the different APPs have the authority of accessing the platform. In other words, each APP can realize that different APPs use the message service platform together only by applying a pair of public key and private key to the message service platform, so that the APPs do not need to repeatedly develop the message function provided by the message service platform.

S120, determining an APP of a receiver by adopting a Redis overdue monitoring mechanism, and triggering the sending of the push message.

The data base Redis supports data persistence, data in the memory can be stored in a disk, and the data can be loaded and used again when the disk is restarted. Redis may store key-value type data while also providing storage for data structures such as strings, lists, collections, and the like. Redis can meet the requirement of performing certain behavior after waiting for a certain time in the service by carrying out overdue monitoring on the key. In this embodiment, after the calling party APP has configured the message template, a Redis expiration monitoring mechanism is used to monitor whether a message trigger event corresponding to the message template occurs, and if so, the receiving party APP is determined and the message is triggered to be sent.

Optionally, determining the recipient APP by using a Redis expiration monitoring mechanism may include: determining the upper limit of the monitoring time of a Redis overdue monitoring mechanism, and monitoring a message event corresponding to a message template; and when a target message event with the monitoring time reaching the upper limit of the monitoring time is detected, determining a receiver APP according to the APP corresponding to the target message event.

In this embodiment, a key-value type data may be used to represent a message event corresponding to a message template, and then a Redis expiration monitoring mechanism is used to monitor the key, and when the monitoring time reaches the upper limit of the monitoring time, whether an APP corresponding to the message event is a recipient APP is determined according to whether the message event satisfies a message triggering condition.

For example, taking a scenario that payment is not paid within 30 minutes after the order is generated, the order is automatically closed and the prompt message is sent as an example, the upper limit of the monitoring time is 30 minutes, and monitoring the message event corresponding to the message template can be understood as monitoring the generation duration of the order. When an order is generated, a K-V key value pair is added to Redis, wherein K is an order number, a certain order in a database can be located through K, and V can be any value. By adopting a Redis expiration monitoring mechanism, if a certain K-V key value pair in Redis is monitored to be expired, namely the order corresponding to the key value pair is generated for 30 minutes, the order is located through K. If the order is unpaid, the APP generating the order is considered to meet the message triggering condition, the APP can be used as the APP of the receiver, and the sending of the push message is triggered. If the order is paid, the APP generating the order is considered not to meet the message triggering condition, and the APP cannot be selected as the APP of the receiver.

S130, generating a push message matched with the message template by using the producer and consumer modes of the RabbitMQ, and sending the push message to the APP of the receiver.

In the embodiment, the message service platform integrates Redi s and RabbitMQ based on a Java Spring Boot framework, the appointed time reaching of the pushed message is realized through a Redis overdue monitoring mechanism, and a series of problems of large data volume, persistence, message loss and the like of the pushed message are asynchronously solved through a producer and consumer mode of the RabbitMQ. After the recipient APP is determined, according to the producer and consumer modes of the RabbitMQ, a push message matched with the message template can be generated by the producer, and the consumer sends the push message to the recipient APP.

Optionally, after receiving the push message, the APP of the recipient performs Scheme jump protocol analysis on the push message, determines a jump parameter and a page to be jumped, and jumps from a display page of the push message to the page to be jumped according to the jump parameter.

The Scheme is an intra-page jump protocol, and any page in the APP can be jumped to through the user-defined Scheme jump protocol. Illustratively, a certain page of the APP, such as an advertisement page or a bill page, may be skipped to in a customized manner through a message issued by the server; the APP can jump to a certain page in another APP in a customized manner, for example, when the APP receives a push notification bar message, the APP jumps to application market downloading, updating and evaluating by clicking the notification bar message, or jumps to Paobao payment and the like; the anchor point can be clicked through the H5 page, and the customization jumps to a certain page of the APP. From a technical point of view, the jump for realizing Scheme has two steps: analyzing a Scheme jump protocol; and jumping to a specified page according to the analysis result.

In this embodiment, by setting the Scheme jump protocol, after the receiving party APP receives the push message, the receiving party APP can obtain the jump parameter from the push message according to the parsing rule of the Scheme jump protocol, and jump to the specified page to be jumped from the current display page according to the jump parameter, so that even if the version of the mobile phone operating system of the user is too low or the APP is not upgraded to the latest version, the receiving party APP can also give corresponding prompt information as required, or jump to the specified page, thereby avoiding the situation that the page cannot be jumped.

Optionally, after generating a push message matched with the message template using a producer and consumer model of the RabbitMQ and sending the push message to the recipient APP, the method further includes: storing the detailed content of each sent push message into Redis; and responding to the troubleshooting request, and acquiring the detailed content of the push message stored in the Redis for message analysis and warning.

In this embodiment, for convenience of performing subsequent data analysis and troubleshooting, for each push message sent to the recipient APP, detailed contents of the push message, for example, data such as a client ID, a message content, whether the message is read, a message template title, an actual message sending time, a message type, a skip protocol, a skip parameter, a reading type, and a trigger type, are recorded, and the data are stored in a Redis database. And after a troubleshooting request is received, acquiring the detailed content of the push message from the Redis database for analysis.

Optionally, the method may further include: if the message type configuration request is acquired, encoding to realize a new message type corresponding to the message type configuration request; when the calling party APP configures the message template on the visual configuration interface, the new message type is provided to the calling party APP as an optional item.

In this embodiment, when a configuration request for a new message type is acquired, the platform may rapidly develop the new message type, and add the new message type in an option of the message type when the APP configures the template. For APP, only the corresponding message type option needs to be selected when the message template is configured on the platform, the function does not need to be developed by the APP, and the complexity of the APP for using the function is greatly reduced.

Example two

Fig. 3 is a schematic structural diagram of a message trigger apparatus according to a second embodiment of the present invention. The embodiment is applicable to the case that the calling party APP of the access platform implements message triggering, and the message triggering apparatus may be implemented in the form of hardware and/or software, and may be configured in the electronic device. As shown in fig. 3, the apparatus is applied to a message service platform, where the message service platform integrates a database Redis and a message queue RabbitMQ based on a Spring Boot framework, and includes:

the configuration module 310 is configured to generate a message template in response to a message configuration operation of the calling party APP on the visual configuration interface;

a message triggering module 320, configured to determine a recipient APP by using a Redis expiration monitoring mechanism, and trigger sending of a push message;

and the message pushing module 330 is configured to generate a push message matched with the message template by using the producer and consumer modes of the RabbitMQ, and send the push message to the recipient APP.

Optionally, the method further includes: the key application module is used for responding to a key application request of the calling party APP and feeding back a pair of public key and private key to the calling party APP before responding to message configuration operation of the calling party APP on the visual configuration interface and generating a message template; and the public key and the private key are used for calling the APP of the calling party to access the message service platform for function calling.

Optionally, the message template includes: template name, message type, jump protocol, jump parameter and message content; the jump protocol comprises the following steps: scheme jump protocol based on Flutter framework.

Optionally, the method further includes: the analysis warning module is used for generating push messages matched with the message template in a producer and consumer mode using the RabbitMQ, sending the push messages to the receiver APP, and then storing the detailed content of each sent push message into the Redis; and responding to the troubleshooting request, and acquiring the detailed content of the push message stored in the Redis for message analysis and warning.

Optionally, the method further includes: the extension module is used for coding and realizing a new message type corresponding to the message type configuration request if the message type configuration request is acquired; when the calling party APP configures the message template on the visual configuration interface, the new message type is provided to the calling party APP as an optional item.

Optionally, the message triggering module 320 is configured to: determining the upper limit of the monitoring time of a Redis overdue monitoring mechanism, and monitoring a message event corresponding to a message template; and when the target message event with the monitoring time reaching the upper limit of the monitoring time is detected, determining a receiver APP according to the APP corresponding to the target message event.

Optionally, after receiving the push message, the recipient APP performs schedule jump protocol analysis on the push message, determines a jump parameter and a page to be jumped, and jumps to the page to be jumped from a display page of the push message according to the jump parameter.

The message triggering device provided by the embodiment of the invention can execute the message triggering method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.

EXAMPLE III

FIG. 4 illustrates a block diagram of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 4, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM)12, a Random Access Memory (RAM)13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM)12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as the message triggered method.

In some embodiments, the message triggering method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the message triggering method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the message triggering method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.

It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.

The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A message triggering method is applied to a message service platform, wherein the message service platform integrates a database Redis and a message queue RabbitMQ based on a Spring Boot framework, and comprises the following steps:

responding to the message configuration operation of the calling application program APP on the visual configuration interface, and generating a message template;

2. The method according to claim 1, before generating a message template in response to a message configuration operation of a caller APP on a visual configuration interface, further comprising:

3. The method of claim 1, wherein the message template comprises: template name, message type, jump protocol, jump parameter and message content; the jump protocol comprises: scheme jump protocol based on Flutter framework.

4. The method of claim 1, after generating a push message matching the message template using a producer and consumer model of a RabbitMQ and sending the push message to the recipient APP, further comprising:

storing the detailed content of each sent push message into Redis;

5. The method of claim 3, further comprising:

if the message type configuration request is obtained, encoding to realize a new message type corresponding to the message type configuration request;

and when the calling party APP configures the message template on the visual configuration interface, providing the new message type as an optional item for the calling party APP.

6. The method of claim 1, wherein determining the recipient APP using a Redis Enable snoop mechanism comprises:

7. The method according to claim 3, wherein after receiving a push message, the recipient APP performs Scheme jump protocol analysis on the push message, determines jump parameters and a page to be jumped, and jumps from a display page of the push message to the page to be jumped according to the jump parameters.

8. A message trigger device is applied to a message service platform, wherein the message service platform integrates a database Redis and a message queue RabbitMQ based on a Spring Boot framework, and comprises:

the message triggering module is used for determining the APP of the receiver by adopting a Redis overdue monitoring mechanism and triggering the sending of the push message;

9. An electronic device, characterized in that the electronic device comprises:

at least one processor; and

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the message triggering method of any one of claims 1-7.

10. A computer-readable storage medium storing computer instructions for causing a processor to implement the message triggering method of any one of claims 1-7 when executed.