Disclosure of Invention
To overcome the problems in the related art, the present specification provides a message pushing method, apparatus, and computer-readable storage medium.
According to a first aspect of embodiments of the present specification, there is provided a message pushing method, applied to a message pushing center, the method including:
receiving a service system in communication connection with the message pushing center, and sending a target message for pushing to a designated client;
determining a target push channel from a plurality of message channels registered by the designated client in the message push center, wherein the message channels comprise mqtt channels communicated with the designated client through mqtt protocols;
and pushing the target message to the appointed client based on the target pushing channel.
According to the message pushing method provided by the application, the message pushing center is in communication connection with the server supporting mqtt protocols,
The pushing the target message to the specified client based on the target pushing channel includes:
When the target pushing channel is the mqtt channel, pushing the target message and the equipment identifier corresponding to the appointed client to a mqtt server, so that the mqtt server pushes the target message to the appointed client through the channel corresponding to the equipment identifier;
The device identifier is information which is acquired by the appointed client after the message pushing center is registered and is used for uniquely identifying the client.
According to the message pushing method provided by the application, the message channel also comprises a system channel set during development of the mobile terminal where the appointed client is located;
The determining a target push channel from a plurality of message channels registered by the specified client in the message push center includes:
determining the target push channel according to the priority of the message channel;
wherein the mqtt channels have a higher priority than the system channels.
According to the message pushing method provided by the application, the pushing of the target message to the designated client based on the target pushing channel comprises the following steps:
Monitoring and feeding back state information of the information transmission capacity of the target push channel;
Analyzing the state information;
When the state information indicates that the current target push channel does not meet a preset transmission condition, updating the target push channel according to the other channel in the system channel and the mqtt channel, and pushing the target message to the appointed client based on the updated target push channel.
According to the message pushing method provided by the application, the pushing of the target message to the designated client based on the target pushing channel further comprises:
Acquiring the current times of pushing the target information by the target pushing channel;
If the times reach a preset value, updating the target pushing channel according to the other channel of the system channel and the mqtt channel, and pushing the target message to the appointed client based on the updated target pushing channel.
According to the message pushing method provided by the application, before receiving the service system in communication connection with the message pushing center and sending the target message for pushing to the designated client, the method further comprises the following steps:
Receiving equipment information and user identification sent by the appointed client, wherein the user identification is determined by user information input when the appointed client is connected with the message pushing center;
Binding the device information with a user identifier to generate the device identifier for pushing and receiving the target message;
and sending the equipment identifier to the appointed client to finish the registration of the appointed client in the message pushing center.
According to the message pushing method provided by the application, before determining the target pushing channel from the message channels registered by the designated client in the message pushing center, the method further comprises:
Checking whether the appointed client is registered in the message pushing center;
If so, executing the step of determining a target push channel from a plurality of message channels registered by the designated client in the message push center;
And if not, storing the target message, and pushing the target message to the appointed client based on the target pushing channel after the appointed client finishes registration.
According to the message pushing method provided by the application, the pushing of the target message to the designated client based on the target pushing channel comprises the following steps:
According to the message structure requirement of the target push channel, adjusting the structure of the target message;
and pushing the adjusted target message to the appointed client.
According to the message pushing method provided by the application, after the target message is pushed to the designated client based on the target pushing channel, the method further comprises the following steps:
receiving a message pushing result returned by the appointed client and updating the state of the target message;
And if the pushing result representing that the target message reaches the specified client is not received within the set time length, the step of pushing the target message to the specified client based on the target pushing channel is re-executed.
According to the message pushing method provided by the application, after the service system in communication connection with the message pushing center is received, the sent target message for pushing to the designated client is sent, the method further comprises:
And setting a message identifier for the target message, and sending the message identifier to the service system so that the service system tracks the state of the target message according to the message identifier.
The application also provides a message pushing device, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the message pushing method according to any one of the above when executing the program.
The application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a message pushing method as described in any of the above.
Compared with the prior art that when different application services need to use the pushing function, the method, the device and the computer readable storage medium for pushing the message in the embodiment of the specification need to separately connect each business pushing service or the pushing service provided by each mobile phone manufacturer to increase the development and maintenance cost of the system, so that the developed message pushing function needs to consume a great deal of manpower and financial resources; and then determining a target pushing channel from a plurality of message channels registered by the designated client in the message pushing center, wherein the target pushing channel is used for pushing the target message to the designated client based on the target pushing channel, and the service center transmits the message to the pushing center by introducing the message pushing center, so that the subsequent delivery of the message is not concerned any more, the problem of system coupling is solved, and the service logic is clearer. Meanwhile, the message channels comprise mqtt channels which are communicated with the appointed client through mqtt protocols, and the effect of one-time development and multi-terminal use is achieved through introducing mqtt channels, so that the labor and financial resources consumed by repeated development are saved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Detailed Description
The technical solutions in the embodiments (or "implementations") of the present application will be clearly and completely described herein with reference to the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated.
If there are terms (e.g., upper, lower, left, right, front, rear, inner, outer, top, bottom, center, vertical, horizontal, longitudinal, lateral, length, width, counterclockwise, clockwise, axial, radial, circumferential, etc.) related to directional indications or positional relationships in embodiments of the present application, such terms are used merely to explain the relative positional relationships, movement, etc. between the components at a particular pose (as shown in the drawings), and if the particular pose is changed, the directional indications or positional relationships are correspondingly changed. In addition, the terms "first", "second", etc. in the embodiments of the present application are used for descriptive convenience only and are not to be construed as indicating or implying relative importance.
The application provides a message pushing method, a message pushing device and a computer readable storage medium. The present application will be described in detail with reference to the accompanying drawings. The features of the examples and embodiments described below may be combined with each other without conflict.
Current mobile-side push functions are mostly implemented by accessing commercial push services (such as aurora push), or using push services provided by various mobile phone manufacturers (such as millet push, and APNS apple system push notification service). When different application services need to use push functions, it is necessary to individually interface with each business push service or push service provided by each handset vendor. There is a large number of duplicate codes and duplicate effort expenditures in between. In summary, the developed message pushing function needs to consume a lot of manpower and financial resources, and the final pushing effect is limited by the bearing capacity of the third party service and cannot be controlled automatically.
When the system needs to have the function of message pushing, independent development is required for different systems and different mobile phone manufacturers, so that the development period is long, and each manufacturer charges service fees, so that the development and maintenance cost of the system is increased. Because of the system depending on the third party, the instantaneity and success rate of message delivery are limited by the stability and service capability of the third party system, and if the third party service fails, the network is unstable or the load is too high, the problems of message push delay, uncontrollable loss and the like can be caused, so that the accuracy and timely progress of the service are affected. Nowadays, enterprises pay more and more attention to information security, and the risk of information leakage is greatly increased by transmitting client information or system internal information to external third parties.
In order to solve the technical problems, the present specification provides a message pushing method.
And introducing a message pushing center, transmitting the message to the message pushing center when the service center needs to send the message, and pushing the message to an application program/client receiving the message by the message pushing center according to the matched channel.
Here, the message pushing center refers to a system for processing and putting messages.
In one embodiment, as shown in fig. 1, fig. 1 is a schematic flow diagram of a service system push message provided in an embodiment of the present disclosure. The message pushing center also comprises a pushing dispatch service module and a pushing distribution service module.
The message pushing process comprises the following steps of;
Step 1, when a business system pushes a target message to a specified client (or logs in a target user of the specified client), the business system firstly sends the target message to a pushing scheduling service module of a message pushing center;
And 1.1, setting a message identifier for the target message. The pushing dispatch service module marks a unique identifier GUID on the target message;
Step 1.2, a pushing scheduling service module matches a target pushing channel according to available channels (such as a system channel, a mqtt channel and the like);
step 1.3, a push dispatch service module stores a target message;
And step 1.4, the message identification is sent to the service system, so that the service system tracks the state of the target message according to the message identification. The pushing dispatch service module returns a unique identifier GUID of the target message to a designated client;
step 1.5, the pushing dispatch service module submits an asynchronous pushing task to the pushing distribution service module so as to start pushing the target message according to the target pushing channel;
and 1.5.1, forming a push instruction, and processing a message format based on the message structure requirement of the target push channel.
Step 1.5.2, respectively pushing a plurality of message channels, preferably selecting mqtt channels for pushing, and switching other message channels to push target messages to a designated client under the condition of failed pushing;
Step 1.5.3, the appointed customer end returns the information of the received message to the pushing and distributing service module;
And step 1.6, the push scheduling service module updates the message state to ensure that the push is successful.
By introducing the message pushing center and mqtt, the effect of one-time development and multi-terminal application is realized, and the manpower and financial resources consumed by repeated development are saved. And the message is pushed by the message pushing center, so that the service center is not concerned with the subsequent delivery of the message, the problem of coupling of a service system is solved, the service logic is clearer, the performance can be adjusted and optimized in a targeted manner, and the user experience is improved.
Fig. 2 is a flow chart of a message pushing method provided based on the above embodiment, including the following steps:
And S100, receiving a service system in communication connection with the message pushing center, and sending a target message for pushing to a designated client.
The business system described herein is a software system internal to the enterprise/provider that applies the message pushing program for handling specific business logic, data management, and interaction with the outside, the functionality of which includes, but is not limited to, pushing messages to users to pass some important event or state change by the user. Such as vehicle management systems in a vehicle enterprise, electric business systems, etc.
The client refers to an application program installed on a user device (such as a mobile phone, a computer, etc.), and is an interface for a user to interact with the server, and the user receives and sends messages by operating the client.
The service system interacts with the message pushing center through a specific interface (such as an API application programming interface provided by the message pushing center), the message pushing center receives the target message sent by the service system, further processes the target message, such as marking the target message with a unique identifier GUID, selecting a pushing channel, storing the message, and the like, and then pushes the message to a target user.
In this embodiment, by establishing the message pushing center, the service system does not need to directly process the pushing process of the message, but sends the message to the message pushing center, and the message pushing center receives and processes the message and pushes the message to the designated client or the target user bound to the designated client. The decoupling of the service system and the message pushing center is formed, so that the service system is more focused on processing core service logic, and the performance can be optimized in a targeted manner.
The client receives the message and needs to register in the message pushing center, and corresponding system channels and self-built mqtt channels are registered according to different systems and brands of the client.
In some embodiments, before the receiving the service system communicatively connected to the message pushing center, the method further includes:
Step a1, receiving equipment information and a user identifier sent by the appointed client, wherein the user identifier is determined by user information input when the appointed client is connected with the message pushing center, and the equipment information is information of mobile equipment for installing the appointed client;
wherein the process comprises:
As shown in fig. 3, fig. 3 is a schematic diagram of a client registration process. The message pushing center comprises a pushing dispatching service module and a member service module.
Step1, client pushing SDK is initialized, and communication connection between the client and a message pushing center is established;
And 2, the client collects basic information and uploads the basic information to the message pushing center, wherein the basic information comprises equipment information of the mobile equipment of the appointed client, such as equipment model information.
Step 2.1, the message pushing center stores basic information;
step 2.2, the message pushing center returns feedback information of the received basic information to the client;
Step 3, the user logs in at the client;
step 3.1, when the login is successful, collecting user login information, obtaining a user identifier partyId, and returning the login information and the user identifier partyId to the client;
And 4, the client calls a binding interface and pushes the device information and the user identifier partyId to the message pushing center.
And a2, binding the equipment information with a user identifier, and generating the equipment identifier for pushing and receiving the target message.
Wherein the process comprises:
And 4.1, the message pushing center identifies the mobile equipment and the user, generates a did equipment identifier, and realizes the binding of the equipment information and the user identifier, wherein the did represents the unique binding identifier of the equipment and the user.
And a step a3 of sending the equipment identifier to the appointed client so as to finish the registration of the appointed client in the message pushing center.
Wherein the process comprises:
and 4.2, the message pushing center returns the did to the client.
In other embodiments, after the receiving the service system communicatively connected to the message pushing center and the target message sent for pushing to the specified client, the method further includes:
And checking whether the appointed client is registered in the message pushing center.
After receiving the message, the message pushing center inquires whether a pushing target client is registered in the message pushing center, if not, the target message is stored, and after the designated client finishes registration, the target message is pushed to the designated client based on the target pushing channel. The target message may be pushed together with other messages after the specified client finishes registration, or pushed after the specified client finishes registration, which is not limited herein.
If the appointed client is registered, acquiring the registered did as a subsequent pushing identifier, pushing a message through a message channel corresponding to the did, namely executing the subsequent step of determining a target pushing channel from a plurality of message channels registered in the message pushing center by the appointed client, and pushing the target message to the appointed client based on the target pushing channel.
S200, determining a target push channel from a plurality of message channels registered by the designated client in the message push center, wherein the message channels comprise mqtt channels communicated with the designated client through mqtt protocols.
In order to ensure the success rate of message pushing, a third pushing channel is still reserved, and in the message pushing process, one channel is selected as a target pushing channel according to actual requirements.
Wherein the mqtt channel includes a mqtt server communicatively coupled to the message push center, the mqtt server supporting the transfer of messages via mqtt protocols. Message pushing can be performed on any terminal through mqtt channels, such as WEB services, vehicle-mounted computers, intelligent home, wearable equipment and the like. In some examples, the message pushing center uses EMQX as mqtt server, the client obtains the di device identifier after the registration of the message pushing center, and the client establishes a long connection with EMQX and listens for the message channel corresponding to the di. In the self-built mqtt channels, the business system typically does not interact directly with the mqtt server, but rather uses the mqtt channels for message pushing through the message pushing center. The message pushing center decides whether to use mqtt channels and how to interact with mqtt servers according to the traffic requirements and the pushing policy.
The system channel is a channel set during development of a mobile terminal (such as a mobile phone, a computer and the like) where the specified client is located, for example, push services provided by various mobile phone manufacturers.
It can be understood that when a plurality of message channels cooperate, in order to avoid collision, an adapted channel is matched from available channels to serve as a target push channel for transmission when pushing a message, and when a push failure occurs according to a current channel push message, other channels are switched to serve as target push channels for pushing the message, so that the success rate of message push is ensured. In some examples, selection/switching of channels may be accomplished by a switch control.
In some embodiments, the determining a target push channel from the plurality of message channels registered by the specified client in the message push center includes:
And determining the target push channel according to the priorities of the message channels.
Furthermore, since current push services rely on third party systems, the immediacy and success rate of message delivery will be limited by the stability and service capabilities of the third party systems. If the third party service fails, the network is unstable or the load is too high, the problems of message pushing delay, uncontrollable loss and the like can be caused, and the user experience is affected.
The self-built mqtt channel avoids using the commercial pushing center on the market, can ensure that information does not flow into a third party, ensures absolute safety of the information, saves expenditure generated by using the commercial pushing center, can completely control the information circulation process, can be optimized in a targeted manner aiming at different business scenes, and ensures delivery efficiency of the information. Therefore, the mqtt channels are set to have a priority higher than that of the system channels, and mqtt channels are preferentially used as target push channels.
The mqtt channels are used for receiving the messages, so that the success rate of message pushing is guaranteed, a third party pushing channel is reserved, and whether the third party pushing channel is pushed or not can be controlled through a switch. This section of content is specifically introduced when the next section pushes the target message.
S300, pushing the target message to the appointed client based on the target pushing channel.
And the message pushing center pushes the target message to the designated client subscribed to the corresponding theme through the target pushing channel.
In order to ensure successful pushing of the message, the structure of the target message needs to be adjusted according to different channel attributes so as to adapt to the target pushing channel. In some embodiments, the pushing the target message to the specified client based on the target push channel includes:
According to the message structure requirement of the target push channel, adjusting the structure of the target message;
and pushing the adjusted target message to the appointed client.
In some embodiments, if the message pushing center first selects mqtt channels to push and listens to the message pushing result, the message pushing center pushes the sent target message and the didinformation to the mqtt server, and the mqtt server processes mqtt protocol message transmission and pushes the target message to the client (or app) subscribed to the corresponding topic. Specifically, mqtt server obtains long link channel corresponding to appointed client through the did screening channel, and pushes target message to the channel, finally reaching appointed client.
Specifically, the pushing the target message to the specified client based on the target pushing channel includes:
When the target pushing channel is the mqtt channel, pushing the target message and a fid device identifier corresponding to the specified client to a mqtt server, so that the mqtt server pushes the target message to the specified client through a channel corresponding to the device identifier;
The message pushing center is in communication connection with a server supporting mqtt protocols. The device identifier is information for uniquely identifying the client, which is acquired by the specified client after the registration of the message pushing center.
As an example, as shown in fig. 4, fig. 4 is an interaction diagram of mqtt servers and a message pushing center. The process comprises the following steps:
Step b1, when the client registers to the message pushing center, the client establishes connection with the message pushing center, and transmits equipment information and user information to obtain a did equipment identifier returned by the message pushing center, wherein the did is a set of the did equipment identifier;
step b2, the client is appointed to establish long connection with mqtt server;
Step b3, the message pushing center pushes the target message sent to the appointed client (or the target user logging in the appointed client) to the mqtt server;
Step b4, mqtt server returns feedback information representing the received target message to the message pushing center;
Step b5, mqtt, the server finds out the corresponding dids according to the user information given by the message pushing center and sends the target message to the appointed client (or logs in the target user of the appointed client);
step b6, the appointed customer end feeds back the information of the received message to the message pushing center;
Step b7, the message pushing center feeds back the confirmation of the received message;
step b9, after the user reads the target message, notifying the message pushing center of the read message;
Step b10, the message pushing center feeds back the confirmation that the read message is received.
It should be noted that the description of the status of the feedback message (e.g., "read message") is merely an example, and is not limited to the specific example.
In this embodiment, the mqtt channel is used as a self-built message pushing channel, which avoids the risk of information leakage, achieves the controllability and reliability of the whole link, provides another self-built channel different from the third party channel, increases the timeliness and stability of message pushing, and enhances the receiving capability of the system. And because the message pushing function is independent, developers can perform special tuning aiming at the performance of the message pushing function. Parameters such as the frequency, the priority, the concurrency processing capacity and the like of message pushing can be adjusted according to different service requirements and user scenes.
In other embodiments, the mqtt channels are used for receiving the message first, so that in order to ensure the success rate of message pushing, a third party pushing channel is still reserved, and whether the third party pushing channel/system channel is pushed or not can be controlled by a switch. The switch control may be manually controlled by a background manager in the message pushing center, or may be automatically controlled according to the pushed state information, which is not limited herein.
Specifically, the pushing the target message to the specified client based on the target pushing channel includes:
Monitoring and feeding back state information of the information transmission capacity of the target push channel;
Analyzing the state information;
When the state information indicates that the current target push channel does not meet a preset transmission condition, updating the target push channel according to the other channel in the system channel and the mqtt channel, and pushing the target message to the appointed client based on the updated target push channel.
In some embodiments, the status information of the transmission capability includes parameters such as a frequency, a priority, and a concurrent processing capability of message pushing, for example, when a target message is pushed based on mqtt channels as a target push channel, if there is an excessive load, which affects the instantaneity and stability of pushing, the switch control is switched to a third party push channel/system channel as the target push channel to push the target message.
In other embodiments, the status information of the transmission capability further includes information such as a push duration, a push number, etc., and if the push fails within the set duration and the retry range, whether to push the third party push channel/system channel is controlled according to the switch.
Specifically, for the pushing times, the pushing the target message to the specified client based on the target pushing channel further includes:
Acquiring the current times of pushing the target information by the target pushing channel;
If the times reach a preset value, updating the target pushing channel according to the other channel of the system channel and the mqtt channel, and pushing the target message to the appointed client based on the updated target pushing channel.
Specifically, for the push duration, after the target message is pushed to the specified client based on the target push channel, the method further includes:
receiving a message pushing result returned by the appointed client and updating the state of the target message;
And if the pushing result representing that the target message reaches the specified client is not received within the set time length, the step of pushing the target message to the specified client based on the target pushing channel is re-executed.
The two cases can be applied independently or combined with each other. As an example, if the set duration is10 s, the preset number of pushing times is 3, and the current target pushing channel is mqtt channels. If no response of the designated client is received within 10s after the target message is pushed through the current target pushing channel, pushing is performed again based on the target pushing channel, the channel is switched until the pushing is failed for 3 times, and the third party pushing channel/system channel is controlled to serve as the target pushing channel to continuously push the target message to the designated client, so that the success rate of message pushing is ensured.
Compared with the prior art that when different application services need to use a pushing function, the application needs to independently butt joint each business pushing service or pushing service provided by each mobile phone manufacturer to increase the system development and maintenance cost, so that the developed message pushing function needs to consume a great deal of manpower and financial resources; and then determining a target pushing channel from a plurality of message channels registered by the designated client in the message pushing center, wherein the target pushing channel is used for pushing the target message to the designated client based on the target pushing channel, and the service center transmits the message to the pushing center by introducing the message pushing center, so that the subsequent delivery of the message is not concerned any more, the problem of system coupling is solved, and the service logic is clearer. Meanwhile, the message channels comprise mqtt channels which are communicated with the appointed client through mqtt protocols, and the effect of one-time development and multi-terminal use is achieved through introducing mqtt channels, so that the labor and financial resources consumed by repeated development are saved.
Based on the same application concept as the method, the embodiment of the application also provides a message pushing device, as shown in fig. 5.
The device comprises:
A message receiving module 502, configured to receive a target message sent by a service system communicatively connected to the message pushing center and used for pushing the target message to a specified client;
A channel determining module 504, configured to determine a target push channel from a plurality of message channels registered by the specified client in the message push center, where the plurality of message channels includes mqtt channels that communicate with the specified client through a mqtt protocol;
And a message pushing module 506, configured to push the target message to the specified client based on the target push channel.
The implementation process of the functions and actions of each module/sub-module/unit in the above device is specifically detailed in the implementation process of the corresponding steps in the above method, so that the same technical effects can be achieved, and will not be described herein again.
Fig. 6 illustrates a physical structure of a message pushing device, as shown in fig. 6, which may include a processor 810, a communication interface (CommunicationsInterface) 820, a memory 830, and a communication bus 840, wherein the processor 810, the communication interface 820, and the memory 830 perform communication with each other through the communication bus 840. The processor 810 may invoke logic instructions in the memory 830 to perform the message pushing method.
Further, the logic instructions in the memory 830 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a Read-only memory (ROM), a random access memory (RAM, randomAccessMemory), a magnetic disk, an optical disk, or other various media capable of storing program codes.
In another aspect, the present application also provides a computer program product comprising a computer program storable on a non-transitory computer readable storage medium, the computer program, when executed by a processor, being capable of performing the message pushing method provided by the methods described above.
In yet another aspect, the present application also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, is implemented to perform the message pushing method provided by the above methods.
It should be noted that the technical solutions or technical features described in the above embodiments may be combined or supplemented with each other without generating a conflict. The scope of the present application is not limited to the exact construction described in the above embodiments and illustrated in the accompanying drawings, but modifications, equivalents, improvements, etc. that fall within the spirit and principle of the present application are intended to be included in the scope of the present application.