Message pushing method and device, electronic equipment and storage medium
By providing a message push method in the Internet of Vehicles project, using the message template to determine the target message, channel and receiver, and push it according to the connection status of the receiver, the problem of high development costs in the Internet of Vehicles project is solved, efficient message processing is achieved and development costs are reduced.
Patent Information
- Application Number
- CN202510375777.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-27
- Publication Date
- 2025-05-06
AI Technical Summary
In the Internet of Vehicles project, due to the different push types and the sending and receiving ends of message push, each end needs to select and integrate different technical components, resulting in the problem of high development costs.
Provide a message push method, by receiving a request from the message sending end, obtaining a matching message template, determining the target message, message channel and message receiving end to be pushed, and pushing according to the connection status of the receiving end.
By integrating each message channel, the message to be pushed and the push channel and destination of the message sending end are determined based on the message template, and communication between multiple channels and multiple terminals or servers is realized, which improves message processing efficiency and reduces development costs.
Smart Images
Figure CN119946008A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of Internet of Vehicles, and in particular to a message push method, device, electronic device and storage medium. Background Art
[0002] With the development of new-generation information and communication technologies, the application of Internet of Vehicles is becoming more and more extensive. Internet of Vehicles uses moving vehicles as information perception objects, and with the help of new-generation information and communication technologies, it realizes all-round network connections between vehicles and cloud platforms, vehicles and vehicles, vehicles and roads, vehicles and people, and inside vehicles, thereby improving the overall intelligent driving level of vehicles, providing users with safe, comfortable, intelligent, and efficient driving experience and transportation services, while improving traffic operation efficiency and enhancing the intelligence level of social transportation services.
[0003] In the Internet of Vehicles project, there are many scenarios that require message push, such as: vehicle abnormality reminders, holiday greetings, smart recommendations, car-handling interconnection, etc. However, due to the different push types and the different senders and receivers of message push (OEMs, third parties, car computers, mobile phones, etc.), each end needs to select and integrate different technical components according to the actual scenario, resulting in high development costs. Summary of the invention
[0004] The present application provides a message push method for solving the problem of high development cost in the prior art.
[0005] According to one aspect of the present application, a message push method is provided, the method comprising:
[0006] Receive a message push request from the message sender, and obtain a message template that matches the message push request;
[0007] Determine the target message, message channel and message receiving end to be pushed according to the message template;
[0008] The connection status of the message receiving end is queried. When it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel.
[0009] In a possible implementation, before receiving the message push request from the message sender, the process includes:
[0010] Get the connection request sent by the message sender;
[0011] Authenticate the message sender based on the connection request;
[0012] When the authentication is passed, the connection status of the message sender is online.
[0013] In a possible implementation, the message push request includes a message type;
[0014] The message templates matched by the above request for getting message push include:
[0015] The message template is obtained by matching the message type and the tag of the message sender.
[0016] In yet another possible implementation, after querying the connection status of the message receiving end, the following steps are included:
[0017] When it is determined that the connection status of the message receiving end is offline, the target message is saved in the task queue to be pushed;
[0018] After a preset time interval, the connection status of the message receiving end is queried. When it is determined that the connection status of the message receiving end is online, the target message is obtained from the task queue to be pushed, and the target message is pushed to the message receiving end.
[0019] In another possible implementation, before receiving the message push request from the message sender, the following steps are included:
[0020] Get the preset message type, as well as the message channel, message source and message destination that match the message type;
[0021] Generate message templates based on message type, message channel, message source and message destination.
[0022] In another possible implementation, the step of determining the target message to be pushed, the message channel, and the message receiving end according to the message template includes:
[0023] According to the message module analysis, the message type, message channel, message source and message destination are obtained;
[0024] Generate a target message to be pushed based on at least one of a message type, a message channel, a message source, and a message destination;
[0025] Determine the message receiving end corresponding to the message destination.
[0026] In another possible implementation, after the target message is pushed to the message receiving end through the message channel, the following steps are included:
[0027] Save the target message to the preset push task queue.
[0028] According to another aspect of an embodiment of the present application, a message push device is provided, the device comprising:
[0029] The receiving module is used to receive the message push request from the message sender and obtain the message template matched by the message push request;
[0030] A determination module is used to determine the target message to be pushed, the message channel and the message receiving end according to the message template;
[0031] The push module is used to query the connection status of the message receiving end. When it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel.
[0032] In another possible implementation, before receiving the message push request from the message sender, the receiving module is used to:
[0033] Get the connection request sent by the message sender;
[0034] Authenticate the message sender based on the connection request;
[0035] When the authentication is passed, the connection status of the message sender is online.
[0036] In another possible implementation, the message push request includes a message type;
[0037] When obtaining the message template matched by the message push request, the above receiving module is used to:
[0038] The message template is obtained by matching the message type and the tag of the message sender.
[0039] In another possible implementation, after querying the connection status of the message receiving end, the push module is used to:
[0040] When it is determined that the connection status of the message receiving end is offline, the target message is saved in the task queue to be pushed;
[0041] After a preset time interval, the connection status of the message receiving end is queried. When it is determined that the connection status of the message receiving end is online, the target message is obtained from the task queue to be pushed, and the target message is pushed to the message receiving end.
[0042] In another possible implementation, before receiving the message push request from the message sender, the receiving module is used to:
[0043] Get the preset message type, as well as the message channel, message source and message destination that match the message type;
[0044] Generate message templates based on message type, message channel, message source and message destination.
[0045] In another possible implementation, when the determination module determines the target message to be pushed, the message channel, and the message receiving end according to the message template, it is used to:
[0046] According to the message module analysis, the message type, message channel, message source and message destination are obtained;
[0047] Generate a target message to be pushed based on at least one of a message type, a message channel, a message source, and a message destination;
[0048] Determine the message receiving end corresponding to the message destination.
[0049] In another possible implementation, after the push module pushes the target message to the message receiving end through the message channel, it is used to:
[0050] Save the target message to the preset push task queue.
[0051] According to another aspect of the present application, an electronic device is provided, which includes: a memory, a processor, and a computer program stored in the memory, and the processor executes the computer program to implement the steps of the method shown in the first aspect of the present application.
[0052] According to another aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method shown in the first aspect of the present application are implemented.
[0053] The beneficial effects of the technical solution provided by this application are:
[0054] The message push method, device, electronic device and storage medium provided by the present application can obtain the message template matched by the message push request, and then determine the target message to be pushed, the message channel and the message receiving end according to the message template; then query the connection status of the message receiving end, and when it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel. The embodiment of the present application integrates each message channel, and can determine the message to be pushed at the message sending end, the push channel and the push destination, that is, the message receiving end, based on the message template. By integrating multiple message components, communication between multiple channels and multiple terminals or service ends (that is, the message sending end and the message receiving end) can be realized, which is different from the prior art of integrating each terminal or service end with different message components, effectively improving the message processing efficiency and reducing the development cost. BRIEF DESCRIPTION OF THE DRAWINGS
[0055] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0056] Figure 1 A flowchart of a message push method provided in an embodiment of the present application;
[0057] Figure 2 A flowchart of an exemplary message push method provided in an embodiment of the present application;
[0058] Figure 3 A schematic diagram of the structure of a message push device provided in an embodiment of the present application;
[0059] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0060] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.
[0061] Various structural schematic diagrams according to embodiments of the present disclosure are shown in the accompanying drawings. These figures are not drawn to scale, and some details are magnified and some details may be omitted for the purpose of clear expression. The shapes of various regions and layers shown in the figures and the relative sizes and positional relationships therebetween are only exemplary, and may deviate in practice due to manufacturing tolerances or technical limitations, and those skilled in the art may further design regions / layers with different shapes, sizes, and relative positions according to actual needs.
[0062] In the context of the present disclosure, when a layer / element is referred to as being "on" another layer / element, the layer / element may be directly on the other layer / element or an intervening layer / element may exist between them. In addition, if a layer / element is "on" another layer / element in one orientation, the layer / element may be "below" the other layer / element when the orientation is reversed.
[0063] In the Internet of Vehicles project, there are many scenarios that require message push, such as: vehicle abnormality reminders, holiday greetings, smart recommendations, car-handling interconnection, etc. However, due to the different push types and the different senders and receivers of message push (OEMs, third parties, car computers, mobile phones, etc.), each end needs to select and integrate different technical components according to the actual scenario, resulting in high development costs.
[0064] Based on the above technical problems, some embodiments of the present application obtain the message template matched by the message push request, and then determine the target message to be pushed, the message channel and the message receiving end according to the message template; then query the connection status of the message receiving end, and when it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel. The embodiments of the present application integrate various message channels, and can determine the message to be pushed at the message sending end, the push channel and the push destination, i.e., the message receiving end, based on the message template. It can be integrated through a variety of message components to realize communication between multiple channels and multiple terminals or service ends (i.e., the message sending end and the message receiving end). It is different from the prior art that each terminal or service end is integrated with different message components, which effectively improves the message processing efficiency and reduces the development cost.
[0065] The following is a detailed description of the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0066] The present application provides a message push method, such as Figure 1 As shown, it can be applied to the message center of the Internet of Vehicles server, and the method includes:
[0067] S101, receiving a message push request from a message sender, and obtaining a message template matched by the message push request.
[0068] S102, determining the target message to be pushed, the message channel and the message receiving end according to the message template.
[0069] Among them, message channels may include Personal Push, Jiguang Push, MQTT (Message Queuing Telemetry Transport), WebSocket (a protocol for full-duplex communication over a single TCP connection), etc.
[0070] Specifically, the message components required by each message channel may be integrated into the message center, so that the message center can communicate with the message sending end or the message receiving end through different message channels.
[0071] S103, querying the connection status of the message receiving end, and when it is determined that the connection status of the message receiving end is online, pushing the target message to the message receiving end through the message channel.
[0072] Specifically, the target message may be sent to the message receiving end through a message channel in an asynchronous communication manner.
[0073] The embodiment of the present application obtains the message template matched by the message push request, and then determines the target message to be pushed, the message channel and the message receiving end according to the message template; then queries the connection status of the message receiving end, and when it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel. The embodiment of the present application integrates each message channel, and can determine the message to be pushed at the message sending end, the push channel and the push destination, that is, the message receiving end, based on the message template. It can be integrated through a variety of message components to realize multi-channel multi-terminal or service end (that is, the message sending end and the message receiving end). Different from the prior art that integrates each terminal or service end with different message components, it effectively improves the message processing efficiency and reduces the development cost.
[0074] A possible implementation method is provided in an embodiment of the present application. Before receiving the message push request from the message sender, the method includes:
[0075] S201, obtaining a connection request sent by a message sender.
[0076] S202, authenticate the message sender based on the connection request; if the authentication is successful, the connection state of the message sender is online. If the authentication is not successful, a reminder that the connection cannot be made is returned.
[0077] Specifically, the client or server can use the secret key to connect to the message center's information reporting, or establish channels and other interfaces (as needed) according to the actual use of the message channel to achieve connection with the message center. After the connection is successful, push messages can be received or sent.
[0078] Optionally, different from the prior art in which the message sending end is connected to each message vendor and message component respectively, the message sending end in the present application only needs to be connected to the message center to conveniently provide various types of message sending and receiving capabilities, effectively saving developers' learning and development costs.
[0079] A possible implementation method is provided in an embodiment of the present application, wherein the message push request includes a message type;
[0080] The message templates matched by the above request for getting message push include:
[0081] The message template is obtained by matching the message type and the tag of the message sender.
[0082] Among them, the message type can be the corresponding message push scenario, such as vehicle abnormality reminder, maintenance reminder, traffic threshold reminder, vehicle condition, etc.
[0083] A possible implementation method is provided in an embodiment of the present application. After the connection status of the query message receiving end is queried, the method includes:
[0084] S301, when it is determined that the connection state of the message receiving end is offline, the target message is saved in a task queue to be pushed.
[0085] S302, querying the connection status of the message receiving end after a preset time interval, and when it is determined that the connection status of the message receiving end is online, obtaining the target message from the task queue to be pushed, and pushing the target message to the message receiving end.
[0086] A possible implementation method is provided in an embodiment of the present application. Before receiving the message push request from the message sender, the method includes:
[0087] S401, obtaining a preset message type, and a message channel, message source, and message destination matching the message type;
[0088] S402, generating a message template based on the message type, message channel, message source and message destination.
[0089] Among them, the message source is the message sender, and the message destination is the message receiver.
[0090] Specifically, the message template can also include different message attributes. For example, when the message template is a message template for a third-party system to push messages to a car application through a push channel, its message attributes can support the configuration of message titles, contents (supporting placeholder configuration) and custom messages; when the message template is the vehicle condition information pushed by the car system to the vehicle APP on the owner's mobile phone through WebSocket, its message attributes can be configured as a custom transparent message.
[0091] The embodiments of the present application can realize personalized customization and management of message content by configuring various message templates, which can effectively improve user experience.
[0092] In an embodiment of the present application, a possible implementation method is provided, wherein the target message to be pushed, the message channel, and the message receiving end are determined according to the message template, including:
[0093] S501, obtaining the message type, message channel, message source and message destination according to the message module analysis;
[0094] S502, generating a target message to be pushed based on at least one of a message type, a message channel, a message source, and a message destination;
[0095] S503, determining the message receiving end corresponding to the message destination.
[0096] A possible implementation method is provided in an embodiment of the present application. After the target message is pushed to the message receiving end through the message channel, the method includes:
[0097] Save the target message to the preset push task queue.
[0098] In other embodiments, after the target message is pushed to the message receiving end through the message channel, the message receiving end can return a push success notification to the message center after receiving the target message. The message center can also save the above push success notification to the push task queue to achieve full life cycle management of the message and provide technical support for developers.
[0099] Specifically, the message center can record the push records of each message channel through the push task queue or statistical report, which is convenient for analyzing the health of the user's vehicle and further improving the user experience.
[0100] In order to better understand the above message push method, Figure 2 An example of a message push method of the present application is described in detail, and the method comprises the following steps:
[0101] S601, the message sending end sends a message push request to the message center.
[0102] The message push request includes a message type.
[0103] S602: The message center obtains a message template by matching the message type and the tag of the message sender.
[0104] Among them, the message type can be the corresponding message push scenario, such as vehicle abnormality reminder, maintenance reminder, traffic threshold reminder, vehicle condition, etc.
[0105] S603, the message center determines the target message to be pushed, the message channel and the message receiving end according to the message template.
[0106] Among them, message channels may include Personal Push, Jiguang Push, MQTT (Message Queuing Telemetry Transport), WebSocket (a protocol for full-duplex communication over a single TCP connection), etc.
[0107] Specifically, the message components required by each message channel may be integrated into the message center, so that the message center can communicate with the message sending end or the message receiving end through different message channels.
[0108] S604, the message center queries the connection status of the message receiving end. When it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel in an asynchronous communication manner.
[0109] The present application embodiment provides a message push device, such as Figure 3 As shown, the message push device 30 may include: a receiving module 301, a determining module 302 and a push module 303;
[0110] The receiving module 301 is used to receive a message push request from a message sender and obtain a message template matched by the message push request;
[0111] A determination module 302 is used to determine the target message to be pushed, the message channel and the message receiving end according to the message template;
[0112] The push module 303 is used to query the connection status of the message receiving end, and when it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel.
[0113] A possible implementation method is provided in an embodiment of the present application. Before receiving a message push request from a message sending end, the receiving module 301 is used to:
[0114] Get the connection request sent by the message sender;
[0115] Authenticate the message sender based on the connection request;
[0116] When the authentication is passed, the connection status of the message sender is online.
[0117] A possible implementation method is provided in an embodiment of the present application, wherein the message push request includes a message type;
[0118] When acquiring the message template matched by the message push request, the receiving module 301 is used to:
[0119] The message template is obtained by matching the message type and the tag of the message sender.
[0120] A possible implementation method is provided in an embodiment of the present application. After querying the connection status of the message receiving end, the push module 303 is used to:
[0121] When it is determined that the connection status of the message receiving end is offline, the target message is saved in the task queue to be pushed;
[0122] After a preset time interval, the connection status of the message receiving end is queried. When it is determined that the connection status of the message receiving end is online, the target message is obtained from the task queue to be pushed, and the target message is pushed to the message receiving end.
[0123] A possible implementation method is provided in an embodiment of the present application. Before receiving a message push request from a message sending end, the receiving module 301 is used to:
[0124] Get the preset message type, as well as the message channel, message source and message destination that match the message type;
[0125] Generate message templates based on message type, message channel, message source and message destination.
[0126] In an embodiment of the present application, a possible implementation is provided. When the determination module 302 determines the target message to be pushed, the message channel, and the message receiving end according to the message template, it is used to:
[0127] According to the message module analysis, the message type, message channel, message source and message destination are obtained;
[0128] Generate a target message to be pushed based on at least one of a message type, a message channel, a message source, and a message destination;
[0129] Determine the message receiving end corresponding to the message destination.
[0130] A possible implementation method is provided in an embodiment of the present application. After the push module 303 pushes the target message to the message receiving end through the message channel, it is used to:
[0131] Save the target message to the preset push task queue.
[0132] The device of the embodiments of the present application can execute the method provided by the embodiments of the present application, and the implementation principles are similar. The actions performed by each module in the device of each embodiment of the present application correspond to the steps in the method of each embodiment of the present application. For the detailed functional description of each module of the device, please refer to the description in the corresponding method shown in the previous text, which will not be repeated here.
[0133] The embodiment of the present application obtains the message template matched by the message push request, and then determines the target message to be pushed, the message channel and the message receiving end according to the message template; then queries the connection status of the message receiving end, and when it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel. The embodiment of the present application integrates each message channel, and can determine the message to be pushed at the message sending end, the push channel and the push destination, that is, the message receiving end, based on the message template. It can be integrated through a variety of message components to realize multi-channel multi-terminal or service end (that is, the message sending end and the message receiving end). Different from the prior art that integrates each terminal or service end with different message components, it effectively improves the message processing efficiency and reduces the development cost.
[0134] In an embodiment of the present application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory, and the processor executes the above-mentioned computer program to implement the steps of the message push method. Compared with the related art, it can be realized that: the embodiment of the present application obtains the message template matched by the message push request, and then determines the target message to be pushed, the message channel and the message receiving end according to the message template; then queries the connection status of the message receiving end, and when it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel. In an embodiment of the present application, by integrating each message channel, the message to be pushed and the push channel and the push destination, i.e., the message receiving end, of the message sending end can be determined based on the message template, and can be integrated through a variety of message components to realize communication between multi-channel and multi-terminals or service ends (i.e., the message sending end and the message receiving end), which is different from the prior art that each terminal or service end is integrated with different message components, effectively improving the message processing efficiency and reducing the development cost.
[0135] In an alternative embodiment, an electronic device is provided, such as Figure 4 As shown, Figure 4 The electronic device 700 shown includes: a processor 701 and a memory 703. The processor 701 and the memory 703 are connected, such as through a bus 702. Optionally, the electronic device 700 may also include a transceiver 704, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 704 is not limited to one, and the structure of the electronic device 700 does not constitute a limitation on the embodiments of the present application.
[0136] Processor 701 may be a CPU (Central Processing Unit), a general purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 701 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0137] The bus 702 may include a path to transmit information between the above components. The bus 702 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 702 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0138] The memory 703 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage medium, other magnetic storage devices, or any other medium that can be used to carry or store computer programs and can be read by a computer, without limitation herein.
[0139] The memory 703 is used to store the computer program for executing the embodiment of the present application, and the execution is controlled by the processor 701. The processor 701 is used to execute the computer program stored in the memory 703 to implement the steps shown in the above method embodiment.
[0140] The electronic devices include, but are not limited to, mobile terminals such as mobile phones, notebook computers, PADs, etc., and fixed terminals such as digital TVs, desktop computers, etc.
[0141] In an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method shown in the first aspect of the embodiment of the present application are implemented.
[0142] In the above description, the technical details such as the patterning of each layer are not described in detail. However, those skilled in the art should understand that various technical means can be used to form layers, regions, etc. of desired shapes. In addition, in order to form the same structure, those skilled in the art can also design methods that are not completely the same as the methods described above. In addition, although the various embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage.
[0143] The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than that shown or described in the drawings.
[0144] It should be understood that, although each operation step is indicated by arrows in the flowchart of the embodiment of the present application, the implementation order of these steps is not limited to the order indicated by the arrows. Unless clearly stated herein, in some implementation scenarios of the embodiment of the present application, the implementation steps in each flowchart can be performed in other orders according to demand. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on actual implementation scenarios. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage in these sub-steps or stages may also be executed at different times respectively. In different scenarios of execution time, the execution order of these sub-steps or stages may be flexibly configured according to demand, and the embodiment of the present application does not limit this.
[0145] The above is only an optional implementation method for some implementation scenarios of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the technical concept of the solution of the present application, other similar implementation methods based on the technical ideas of the present application are also within the protection scope of the embodiments of the present application.
[0146] Although the preferred embodiments of the present application have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.
[0147] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
Claims
1. A message push method, characterized in that: The method comprises: Receive a message push request from a message sender, and obtain a message template that matches the message push request; Determine the target message to be pushed, the message channel and the message receiving end according to the message template; The connection status of the message receiving end is queried, and when it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel.
2. The method according to claim 1, characterized in that Before receiving the message push request from the message sender, the method includes: Get the connection request sent by the message sender; authenticating the message sender based on the connection request; When the authentication is passed, the connection status of the message sending end is online.
3. The method according to claim 1, characterized in that: The message push request includes a message type; The obtaining the message template matched by the message push request includes: A message template is obtained by matching the message type and the tag of the message sender.
4. The method according to claim 1, characterized in that: After querying the connection status of the message receiving end, the method includes: When it is determined that the connection state of the message receiving end is offline, the target message is saved in a task queue to be pushed; The connection status of the message receiving end is queried after a preset time interval, and when it is determined that the connection status of the message receiving end is online, the target message is obtained from the task queue to be pushed, and the target message is pushed to the message receiving end.
5. The method according to claim 1, characterized in that Before receiving the message push request from the message sender, the method includes: Obtain a preset message type, as well as a message channel, message source, and message destination that match the message type; A message template is generated based on the message type, message channel, message source and message destination.
6. The method according to claim 5, characterized in that The step of determining the target message to be pushed, the message channel, and the message receiving end according to the message template includes: According to the message module, the message type, message channel, message source and message destination are obtained; Generate a target message to be pushed based on at least one of the message type, message channel, message source and message destination; Determine the message receiving end corresponding to the destination of the message.
7. The method according to claim 1, characterized in that After the target message is pushed to the message receiving end through the message channel, the method includes: The target message is saved in a preset push task queue.
8. A message push device, characterized in that: The device comprises: A receiving module, used for receiving a message push request from a message sending end, and obtaining a message template matched by the message push request; A determination module, used to determine the target message to be pushed, the message channel and the message receiving end according to the message template; The push module is used to query the connection status of the message receiving end, and when it is determined that the connection status of the message receiving end is online, the target message is pushed to the message receiving end through the message channel.
9. An electronic device, characterized in that: The method is characterized in that it comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 7 when executing the computer program.
10. A storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.