CN113239297A - Message pushing method, system and storage medium - Google Patents
Message pushing method, system and storage medium Download PDFInfo
- Publication number
- CN113239297A CN113239297A CN202110268280.4A CN202110268280A CN113239297A CN 113239297 A CN113239297 A CN 113239297A CN 202110268280 A CN202110268280 A CN 202110268280A CN 113239297 A CN113239297 A CN 113239297A
- Authority
- CN
- China
- Prior art keywords
- message
- push
- pushing
- terminal
- template
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 86
- 238000003860 storage Methods 0.000 title claims abstract description 23
- 238000013507 mapping Methods 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 13
- 238000007781 pre-processing Methods 0.000 claims description 8
- 238000012795 verification Methods 0.000 claims description 8
- 230000006870 function Effects 0.000 description 44
- 238000012545 processing Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 13
- 238000012986 modification Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 7
- 238000011161 development Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000012360 testing method Methods 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
Abstract
The application provides a message pushing method, a system and a storage medium, wherein at least one message template is configured according to configuration requirements; receiving a push request, and adjusting a push message structure of a message template according to the push request; generating a push message according to the adjusted push message structure, and sending the push message to a push terminal; and after the push message is sent, recording the push record, and detecting the push state of whether the push message is successfully pushed. The method realizes simple and quick message pushing, is compatible with the participation and the participation of the original function interface on the whole based on the Apollo configuration message pushing method, and realizes simple and quick message pushing on the basis that the previously applied service function is not influenced.
Description
Technical Field
The present application belongs to the technical field of data processing, and in particular, to a method, a system, and a storage medium for pushing a message.
Background
With the continuous improvement of the APP function, more and more new service scenarios need to be added with the APP message pushing function, so as to meet the requirement of notifying a user of a reminder in the specific service scenario. At present, the App message pushing already covers insurance policy service businesses such as insurance application, correction, claim settlement, renewal and the like, and other business scenes such as rights and interests, account management, disaster assessment and the like. Under the condition, the App message pushing function is optimized, and a simple, universal, easy-to-use and efficient App message pushing framework is created, so that great convenience is brought to development work of various business functions.
Currently, existing message notification methods, such as applet subscription messages and public number messages provided by wechat. Since the using objects are developers of various business systems, the message framework needs to submit applications to WeChat and cannot pass easily when the users want to use the new template. In addition, because the template format of the template is strictly controlled, small programs or public numbers in different industries can only select limited templates, which is very inconvenient. The requirement of a new service scene needs to consider whether the wechat provides an available template, if the wechat is supported, the wechat public platform needs to be additionally configured before development, a random template id and a field format specified by the wechat are obtained after the template is produced, development is carried out according to the template contents, and the public number needs to additionally reconfigure a mapping relation to the UCP platform, which is very inconvenient.
For the traditional version of App message pushing function, because the design scheme from the beginning is different from the current requirement, the current implementation logic is complex, and there are many redundant logics. And many templates are configured in a code hard coding mode, so that once a new message template is required to be added, modification of a plurality of class files is involved, the expansibility is poor, and the method is not friendly to developers.
Disclosure of Invention
The invention provides a message pushing method, a message pushing system and a storage medium, and aims to solve the problems of complex message pushing process and poor expansibility in the prior art.
According to a first aspect of the embodiments of the present application, a message pushing method is provided, which specifically includes the following steps:
configuring at least one message template according to configuration requirements;
receiving a push request, and adjusting a push message structure of a message template according to the push request;
generating a push message according to the adjusted push message structure, and sending the push message to a push terminal;
and after the push message is sent, recording the push record, and detecting the push state of whether the push message is successfully pushed.
In some embodiments of the present application, configuring at least one message template according to configuration requirements specifically includes:
and configuring the number of the message template, the message title, the message body field, the jump target URL and/or the message additional field which need to jump when the message is clicked according to the configuration requirement.
In some embodiments of the present application, receiving a push request, and performing request preprocessing according to the push request before adjusting a push message structure of a message template according to a push parameter of the push request; the request preprocessing according to the push request specifically comprises the following steps:
presetting black and white lists of a pushing party and black and white lists of a pushing terminal;
after receiving a pushing request of a pushing party, acquiring an access password of the pushing party through access interception, and verifying the access password;
after the access password passes the verification, acquiring the identity ID of the pushing party, and comparing the identity ID with the black list and the white list of the pushing party; if the identity ID of the pushing party exists in a white list of the pushing party or the identity ID of the pushing party does not exist in a black list of the pushing party, the pushing party has the authority of pushing messages;
and acquiring a user ID of a push terminal to be pushed by a pushing party, comparing the user ID with a black list and a white list of the push terminal, and if the user ID of the push terminal exists in the white list of the push terminal or the user ID of the push terminal does not exist in the black list of the push terminal, the push terminal has the authority of receiving push messages.
In some embodiments of the present application, before retrieving the message content of the message template and sending the push message to the push terminal, the method further includes:
and determining the type of the push terminal, selecting corresponding push service according to the type of the push terminal, and pushing the message.
In some embodiments of the present application, the method further comprises: if the pushing state is pushing failure, acquiring a message receiving time period of the pushing terminal, and pushing the pushing message again in the corresponding time period, wherein the method specifically comprises the following steps:
acquiring a message receiving time period of a push terminal;
setting the second message pushing time according to the message receiving time period, and timing;
and when the second message pushing time is reached, pushing the message to the pushing terminal again.
In some embodiments of the present application, the method further comprises: the method comprises the following steps of establishing a mapping relation among configuration requirements, message templates and a push terminal in advance:
acquiring configuration requirements of a configuration party, wherein the configuration requirements comprise message titles, message body fields and/or message additional fields;
the configuration requirements, the message templates and the push terminals are in one-to-one correspondence, and a mapping relation is established;
and when receiving a new configuration requirement, determining a message template and a push terminal corresponding to the configuration requirement according to the established mapping relation.
According to a second aspect of the embodiments of the present application, a message pushing system is provided, which specifically includes:
a template configuration module: the message template is used for configuring at least one message template according to configuration requirements;
a message adjusting module: the message template pushing device is used for receiving a pushing request and adjusting a pushing message structure of a message template according to the pushing request;
the message pushing module: the push message structure is used for generating a push message according to the adjusted push message structure and sending the push message to a push terminal;
a push feedback module: the system and the method are used for recording the push record after the push message is sent out and detecting the push state whether the push message is successfully pushed or not.
In some embodiments of the present application, the configuring module configures at least one message template according to a configuration requirement, which specifically includes:
and configuring the number of the message template, the message title, the message body field, the jump target URL and/or the message additional field which need to jump when the message is clicked according to the configuration requirement.
According to a third aspect of the embodiments of the present application, there is provided a message pushing apparatus, including:
a memory: for storing executable instructions; and
the processor is used for connecting with the memory to execute the executable instructions so as to complete the message pushing method.
According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium having a computer program stored thereon; the computer program is executed by a processor to implement a message push method.
By adopting the message pushing method, the message pushing system and the storage medium, at least one message template is configured according to configuration requirements; receiving a push request, and adjusting a push message structure of a message template according to the push request; generating a push message according to the adjusted push message structure, and sending the push message to a push terminal; and after the push message is sent, recording the push record, and detecting the push state of whether the push message is successfully pushed. The method realizes simple and quick message pushing, is compatible with the participation and the participation of the original function interface on the whole based on the Apollo configuration message pushing method, and realizes simple and quick message pushing on the basis that the previously applied service function is not influenced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
a flow chart of steps of a message pushing method according to an embodiment of the application is shown in fig. 1;
a flow chart of steps of a message pushing method according to another embodiment of the present application is shown in fig. 2;
fig. 3 is a schematic structural diagram illustrating a message push system according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a message pushing device according to an embodiment of the present application.
Detailed Description
In the process of implementing the application, the inventor finds that the traditional version of App message pushing function has a design scheme different from the current requirement from the beginning, and the current implementation logic is relatively complex and has a lot of redundant logic. And many templates are configured in a code hard coding mode, so that once a new message template is required to be added, modification of a plurality of class files is involved, the expansibility is poor, and the method is not friendly to developers.
Based on this, the message pushing scheme of the application is compatible with the access and the exit of the original function interface on the whole: although the internal framework design is greatly changed, the functions are inconvenient to maintain, and in order to avoid influencing the service function of the conventional access App message pushing function, the input and output of an interface need to be kept unchanged; therefore, simple and fast message pushing is realized on the basis that the service function which is applied in the past is not influenced.
Specifically, the message pushing method, the message pushing system and the storage medium configure at least one message template according to configuration requirements; receiving a push request, and adjusting a push message structure of a message template according to the push request; generating a push message according to the adjusted push message structure, and sending the push message to a push terminal; and after the push message is sent, recording the push record, and detecting the push state of whether the push message is successfully pushed.
The method realizes the dynamic configuration of the message template based on the Apollo configuration center: the former App message template is written in the code in a hard coding mode, and the new template is directly added to the code. If a new message template exists, a new template format needs to be added into the code, the parameter transmission mode is informed to the service calling party, and the service calling party carries out parameter transmission calling according to parameter agreement to realize pushing. After transformation and optimization, message templates are uniformly configured on a namespace of an Apollo configuration center, if a new function requirement exists, a new template format needs to be added, a calling party only needs to configure a message title, a content format, a skip link and an extension parameter on the Apollo according to the service requirement of the calling party, and then the calling party carries out transmission and calling according to the configuration of the calling party, and the App message pushing frame code does not need to be modified, so that the development efficiency is greatly improved. And if the message file is adjusted, the message file can be directly released and produced in a mode of modifying Apollo configuration, the version flow release of the code nervous soldier version is not required to be modified, and the maintenance is more convenient.
The message template content of the application refers to and supports built-in functions. For some scenarios, it may be necessary to use a special value as an assembly parameter of the template content, such as taking the current time; or additional processing of the incoming parameters, such as monetary text processing, currency addition, unit suffixes and suffixes, etc., may be required. To support this scenario, the new App message framework supports the configuration of preset internal functions in an Apollo configured template. When the message is pushed, the corresponding function is used for processing according to the configuration, and the processing result is added to the actual message content.
In order to make the technical solutions and advantages of the embodiments of the present application more apparent, the following further detailed description of the exemplary embodiments of the present application with reference to the accompanying drawings makes it clear that the described embodiments are only a part of the embodiments of the present application, and are not exhaustive of all embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
Example 1
A flow chart of steps of a message pushing method according to an embodiment of the present application is shown in fig. 1.
As shown in fig. 1, the message pushing method of the present application specifically includes the following steps:
s101, configuring at least one message template according to configuration requirements.
Wherein, the message title, the message body field and/or the additional field of the message template are configured through dynamic parameters and built-in functions.
Each time the configuration party has a message pushing requirement, the configuration party performs configuration of the message template according to a specific configuration requirement corresponding to the message pushing requirement.
The configuration content of the message template specifically includes:
(1) the number of the message template;
(2) a message title;
(3) the content of the message body field;
(4) clicking a jump target URL to which the message needs to be jumped;
(5) other additional fields that need to be binned, such as fields that do not need to be presented by the front end but need to be used subsequently, are for example: a parameter for processing a message click response event, or other parameters for message classification display, etc.
The message header, the message body field and the additional field support dynamic parameters and built-in functions configured according to specific expressions, wherein the dynamic parameters include: # { paramName }; built-in functions such as: f { funcName (# { paramName }) }.
Then, the content configuration is performed through the dynamic parameters and the built-in function. Specifically, the message header, the body field and the additional field are subjected to access conversion, the dynamic parameters and the built-in functions in the Apollo configuration content are analyzed by using the regular matching, and the field values of the corresponding parameter names in the parameters and the calculation results of the built-in functions are replaced into the configuration content.
When configuring the message title, the dynamic title transmitted by the calling party is preferably selected, and then the title is pre-configured by the template.
And regarding the jump target URL, preferentially fetching the URL of the transfer reference, and assembling a complete jump link according to the URL and the jump parameter.
The method is based on an Apollo configuration center, supports dynamic parameters and built-in functions configured according to specific expressions, and firstly, realizes dynamic configuration of a message template, compared with the traditional App message template which is compiled in codes in a hard coding mode, if a new message template is added, a new template format needs to be added in the codes, the message template is uniformly configured on a naming space of the Apollo configuration center, only a calling party needs to configure a message title, a content format, a jump link and an extension parameter on the Apollo according to the business requirement, and then the calling party conducts parameter transmission and calling according to the configuration, and does not need to modify the App message pushing frame codes, so that the development efficiency is greatly improved. Secondly, the content of the message template of the application is transmitted to support the built-in function. For some scenarios, it may be necessary to use a special value as an assembly parameter of the template content, such as taking the current time; or additional processing of the incoming parameters, such as monetary text processing, currency addition, unit suffixes and suffixes, etc., may be required. To support this scenario, the new App message framework supports the configuration of preset internal functions in an Apollo configured template. When the message is pushed, the corresponding function is used for processing according to the configuration, and the processing result is added to the actual message content.
S102, receiving the push request, and adjusting the push message structure of the message template according to the push request.
Specifically, the push request includes a push parameter for adjusting a push message structure. The push message structure comprises whether a message title, a message body field and a message additional field are pushed or not, the sequence in the push message and the total characters of the push message.
The push parameters comprise single push, batch push or directional group push, the push parameters also comprise simplified push, all push, word number limit push and the like, the push message structure is adjusted according to different push requests, and then customized push messages are generated and pushed according to the configured push message structure.
For example, if the push request requires a thin push, the message additional field of the push message is deleted, and only the message header or the message body content is pushed.
If the word count limit is set, the message additional field, the message body field, and the message header are sequentially deleted in the order to meet the requirement.
S103, generating a push message according to the adjusted push message structure, and sending the push message to a push terminal.
After the template is configured, the pushing party sends a message pushing request; and adjusting a push message structure according to the push parameters of the push request, and then pushing the message to the push terminal according to the push inlet.
The push request comprises a message template code and a user ID of the push terminal. Other optional parameters include dynamic message title, dynamic parameter value, additional parameter, jump URL and jump required parameter, etc.
For the internal implementation of the push inlet, the corresponding message template configuration is firstly pulled to an Apollo configuration center according to the transmitted template code, and then parameter conversion processing is carried out.
Preferably, before the message pushing, the method further comprises: and carrying out request preprocessing according to the push request.
Specifically, the request preprocessing includes access interception, security verification of a push party, black and white list setting, push terminal verification and/or the like.
The optional process flow is as follows:
firstly, presetting a blacklist and a white list of a pushing party and a pushing terminal;
after receiving a push request of a push party, intercepting through access, such as password acquisition, and if the push request comprises a correct password, passing verification;
then comparing the identity id of the pushing party with the white list, and if the pushing party exists in the white list, the pushing party has the message pushing authority; alternatively, the identity id of the pushing party may be compared with the blacklist, and if the pushing party does not exist in the blacklist, the pushing party has the message pushing authority;
finally, comparing the user ID of the push terminal with the white list, and if the push terminal exists in the white list, the push terminal has the authority of receiving push messages; alternatively, the identity id of the push terminal may be compared with a blacklist, and if the push terminal does not exist in the blacklist, the push terminal has a right to receive the push message.
Preferably, when the message is pushed to the push terminal, the type of the push terminal needs to be determined, and a corresponding push service is selected according to the type of the push terminal to push the message.
For example, currently, the mainstream types of a mobile phone terminal include an ios terminal and an Android terminal, so that before a message is pushed, it is necessary to first determine whether a push terminal of a push request belongs to the ios terminal or the Android terminal.
If the mobile terminal belongs to the ios terminal, enabling an ios message pushing service to push messages; and if the terminal belongs to the Android terminal, starting an Android message push service to push the message.
S104: and after the push message is sent, recording the push record, and detecting the push state of whether the push message is successfully pushed.
The push record comprises push time, a push terminal and the like.
Specifically, the push record including the sender ID, the message template number, and the push terminal is stored.
Meanwhile, the message pushing state is detected to obtain whether the message pushing is successful or not.
Specifically, if the message pushing fails, a message receiving time period of the pushing terminal is acquired, and the message is pushed again in the corresponding time period.
The specific process is as follows:
1) acquiring a message receiving time period of a push terminal;
2) setting second message pushing time according to the message receiving time period, and timing;
3) and when the second message pushing time is reached, pushing the message to the pushing terminal according to the pushing inlet again.
Because of the app programs of many terminals, the disturbance-free time period can be adjusted according to the use condition of the user and the work and rest time, or the disturbance-free time period is customized for some apps, no notification, message and the like are received within the disturbance-free time, at this time, if message pushing is performed, pushing failure is caused, if the corresponding disturbance-free time period set by the pushing terminal such as the app program is obtained, the message receiving time period of the pushing terminal can be calculated, and the success rate of message pushing is greatly increased.
A flow chart of steps of a message pushing method according to another embodiment of the present application is shown in fig. 2.
As shown in fig. 2, the message pushing method of the present application further includes, after step S104, step S105: and establishing a mapping relation among the configuration requirement, the message template and the push terminal in advance.
Meanwhile, the configuration requirement, the message template and the push terminal of the pre-established mapping relation are configured in the XML file in the form of a preset test case.
Accordingly, the pushing step S102 includes: and calling the preset test case from the XML file to push a message to the push terminal equipment.
The specific treatment process comprises the following steps:
preferably, the configuration requirements of the configurator are obtained, and the configuration requirements can include information such as message content, message title and jump target URL.
Then, the configuration requirements, the message templates and the push terminals are in one-to-one correspondence, and a mapping relation is established.
Secondly, when a new configuration requirement is received, determining a message template and a push terminal corresponding to the configuration requirement according to the established mapping relation;
and finally, calling a pushing inlet of the message template, and pushing the message to the pushing terminal equipment by using the pre-configured message template.
Specifically, the message pushing request includes single pushing, batch pushing, and whole network pushing. Wherein, the single push refers to pushing a message to the user. The batch pushing refers to pushing messages to a plurality of users at the same time, the number of the pushed messages is limited, and in this embodiment, 30 ten thousand messages are pushed at most at one time. The full-network push is to push messages to all users who install the specified APP, for example: as long as the user downloads and opens the APP, the message is pushed to the APP.
Through the step S105, according to different types of message pushing requests of the message platform and the pre-established mapping relation, when the message is pushed, a target user for message pushing can be quickly and intelligently matched only according to the pushing request, the step processes of S101-S104 are not needed to be carried out again, and the pushing efficiency in the message pushing process is improved.
As shown in fig. 2, the embodiment of the present application further includes step S106: and updating and configuring the message templates in the step 101 and the step 105.
Specifically, the method comprises the following steps:
firstly, obtaining updated parameters of template configuration updating, and checking whether the updated parameters are valid, wherein the updated parameters comprise a push entry, a jump target URL, a message body field, a push terminal ID or a storage path corresponding to each configuration format;
and secondly, when the updating parameters are effective, the updating parameters are sent to a configuration end, and the configuration requirements are updated.
Thirdly, editing the content of the configuration information according to a preset analysis rule so as to convert the configuration information into at least one configuration format;
and fourthly, storing the configuration information into a configuration storage path corresponding to each configuration format, and simultaneously finishing the updating of the message template.
By step S106, compared with the existing reconfiguration, the embodiment of the present application reduces unnecessary processes, and improves the template utilization rate and the message pushing efficiency. Meanwhile, the application scene of the existing configuration method is expanded, and the accuracy of message pushing is improved.
The message pushing method comprises the steps of configuring at least one message template according to configuration requirements; receiving a push request, and adjusting a push message structure of a message template according to the push request; generating a push message according to the adjusted push message structure, and sending the push message to a push terminal; and after the push message is sent, recording the push record, and detecting the push state of whether the push message is successfully pushed. The method realizes simple and quick message pushing, is compatible with the participation and the participation of the original function interface on the whole based on the Apollo configuration message pushing method, and realizes simple and quick message pushing on the basis that the previously applied service function is not influenced.
Specifically, the present application has the following advantageous effects;
1. compared with the traditional App message pushing function, the traditional App message pushing function is complex in logic implementation, a lot of redundant logics exist, and the expandability of template configuration realized through code hard coding is poor.
2. According to the app message pushing method, an external caller does not need to change the internal code of the frame if a template needs to be added, and can push the message to the pushing terminal only by configuring the message template to the Apollo configuration center according to the message pushing method and the self requirement and then transmitting and calling the pushing interface according to the configured template.
3. By the app message pushing method, after the app message is released and produced, a title and a content file which need to be changed are found, and only the message template in the Apollo configuration needs to be modified, so that the maintenance cost is reduced.
Example 2
For details not disclosed in the message pushing system of this embodiment, please refer to implementation contents of the message pushing method in other embodiments.
Fig. 3 is a schematic structural diagram of a message push system according to an embodiment of the present application.
As shown in fig. 3, the message pushing system of the present application includes a template configuration module 10, a message adjustment module 20, a message pushing module 30, and a pushing feedback module 40.
In particular, the method comprises the following steps of,
the template configuration module 10: for configuring at least one message template according to configuration requirements.
The message header, the message body field and/or the message additional field of the message template are configured through dynamic parameters and built-in functions.
Configuring based on an Apollo configuration center; the configuration content of the message template comprises a message template number, a message title, a message body field, a jump target URL needing jumping when clicking the message and/or a message additional field.
The message adjustment module 20: and the message template pushing device is used for receiving the pushing request and adjusting the pushing message structure of the message template according to the pushing request.
The push parameters comprise single push, batch push or directional group push, the push parameters also comprise simplified push, total push, word number limit push and the like, and the content of the push messages can be adjusted according to different push parameters.
For example, if the push request requires a thin push, the message additional field of the push message is deleted, and only the message header or the message body content is pushed.
If the word count limit is set, the message additional field, the message body field, and the message header are sequentially deleted in the order to meet the requirement.
The message pushing module 30: and the push message generation module is used for generating a push message according to the adjusted push message structure and sending the push message to the push terminal.
After the template is configured, the pushing party sends a message pushing request; and adjusting a push message structure according to the push parameters of the push request, and then pushing the message to the push terminal according to the push inlet.
The push request comprises a message template code and a user ID of the push terminal. Other optional parameters include dynamic message title, dynamic parameter value, additional parameter, jump URL and jump required parameter, etc.
For the internal implementation of the push inlet, the corresponding message template configuration is firstly pulled to an Apollo configuration center according to the transmitted template code, and then parameter conversion processing is carried out.
Preferably, before the message pushing, the method further comprises: and carrying out request preprocessing according to the push request.
Specifically, the request preprocessing includes access interception, security verification of a push party, black and white list setting, push terminal verification and/or the like.
The optional process flow is as follows:
firstly, presetting a blacklist and a white list of a pushing party and a pushing terminal;
after receiving a push request of a push party, intercepting through access, such as password acquisition, and if the push request comprises a correct password, passing verification;
then comparing the identity id of the pushing party with the white list, and if the pushing party exists in the white list, the pushing party has the message pushing authority; alternatively, the identity id of the pushing party may be compared with the blacklist, and if the pushing party does not exist in the blacklist, the pushing party has the message pushing authority;
finally, comparing the user ID of the push terminal with the white list, and if the push terminal exists in the white list, the push terminal has the authority of receiving push messages; alternatively, the identity id of the push terminal may be compared with a blacklist, and if the push terminal does not exist in the blacklist, the push terminal has a right to receive the push message.
Preferably, when the message is pushed to the push terminal, the type of the push terminal needs to be determined, and a corresponding push service is selected according to the type of the push terminal to push the message.
For example, currently, the mainstream types of the mobile phone terminal include an ios terminal and an Android terminal, and specifically, the push terminal that determines the push request belongs to the ios terminal or the Android terminal.
If the mobile terminal belongs to the ios terminal, enabling an ios message pushing service to push messages; and if the terminal belongs to the Android terminal, starting an Android message push service to push the message.
The push feedback module 40: the system and the method are used for recording the push record after the push message is sent out and detecting the push state whether the push message is successfully pushed or not.
The push record comprises push time, a push terminal and the like.
Specifically, the push record including the sender ID, the message template number, and the push terminal is stored.
Meanwhile, the message pushing state is detected to obtain whether the message pushing is successful or not.
Specifically, if the message pushing fails, a message receiving time period of the pushing terminal is acquired, and the message is pushed again in the corresponding time period.
The specific process is as follows:
1) acquiring a message receiving time period of a push terminal;
2) setting second message pushing time according to the message receiving time period, and timing;
3) and when the second message pushing time is reached, pushing the message to the pushing terminal according to the pushing inlet again.
Preferably, the message pushing system of the present application further includes a mapping module, where the mapping module is configured to establish a mapping relationship among the configuration requirement, the message template, and the pushing terminal in advance.
Meanwhile, the configuration requirement, the message template and the push terminal of the pre-established mapping relation are configured in the XML file in the form of a preset test case.
Accordingly, in the pushing step 102, the method comprises: and calling the preset test case from the XML file to push a message to the push terminal equipment.
The specific treatment process comprises the following steps:
preferably, the configuration requirements of the configurator are obtained, and the configuration requirements can include information such as message content, message title and jump target URL.
Then, the configuration requirements, the message templates and the push terminals are in one-to-one correspondence, and a mapping relation is established.
Secondly, when a new configuration requirement is received, determining a message template and a push terminal corresponding to the configuration requirement according to the established mapping relation;
and finally, calling a pushing inlet of the message template, and pushing the message to the pushing terminal equipment by using the pre-configured message template.
Specifically, the message pushing request includes single pushing, batch pushing, and whole network pushing. Wherein, the single push refers to pushing a message to the user. The batch pushing refers to pushing messages to a plurality of users at the same time, the number of the pushed messages is limited, and in this embodiment, 30 ten thousand messages are pushed at most at one time. The full-network push is to push messages to all users who install the specified APP, for example: as long as the user downloads and opens the APP, the message is pushed to the APP.
Through the mapping module, the method and the device can quickly and intelligently match target users of message pushing according to different types of message pushing requests of the message platform and the pre-established mapping relation only according to the pushing requests during message pushing, and the pushing efficiency in the message pushing process is improved.
Preferably, the embodiment of the present application further includes an update configuration module, where the update configuration module is configured to perform update configuration on the message template.
Specifically, the method comprises the following steps:
firstly, obtaining updated parameters of template configuration updating, and checking whether the updated parameters are valid, wherein the updated parameters comprise a push entry, a jump target URL, a message body field, a push terminal ID or a storage path corresponding to each configuration format;
and secondly, when the updating parameters are effective, the updating parameters are sent to a configuration end, and the configuration requirements are updated.
Thirdly, editing the content of the configuration information according to a preset analysis rule so as to convert the configuration information into at least one configuration format;
and fourthly, storing the configuration information into a configuration storage path corresponding to each configuration format, and simultaneously finishing the updating of the message template.
According to the embodiment of the application, compared with the existing reconfiguration, the configuration module is updated, so that unnecessary processes are reduced, and the template utilization rate and the message pushing efficiency are improved. Meanwhile, the application scene of the existing configuration method is expanded, and the accuracy of message pushing is improved.
In the message pushing system, the template configuration module 10 configures at least one message template according to configuration requirements; the message adjusting module 20 receives the push request, and adjusts the push message structure of the message template according to the push request; the message pushing module 30 generates a push message according to the adjusted push message structure, and sends the push message to the push terminal; the push feedback module 40 records the push record after the push message is sent out, and detects the push state of whether the push message is successfully pushed. The method realizes simple and quick message pushing, is compatible with the participation and the participation of the original function interface on the whole based on the Apollo configuration message pushing method, and realizes simple and quick message pushing on the basis that the previously applied service function is not influenced.
Example 3
For details that are not disclosed in the message pushing device of this embodiment, please refer to specific implementation contents of the automatic vehicle claims settlement method or system in other embodiments.
A schematic structural diagram of a message pushing device 400 according to an embodiment of the present application is shown in fig. 4.
As shown in fig. 4, the message pushing apparatus 400 includes:
the memory 402: for storing executable instructions; and
a processor 401 for interfacing with the memory 402 to execute executable instructions to perform an electronic signature method for generating a PDF based on a template.
Those skilled in the art will appreciate that the diagram 4 is merely an example of the message pushing apparatus 400 and does not constitute a limitation on the message pushing apparatus 400, and may include more or less components than those shown, or combine some of the components, or different components, for example, the message pushing apparatus 400 may also include an input-output device, a network access device, a bus, etc.
The Processor 401 (CPU) may be other general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, or the like. The general purpose processor may be a microprocessor or the processor 401 may be any conventional processor or the like, and the processor 401 is the control center of the message pushing device 400 and connects the various parts of the whole message pushing device 400 by various interfaces and lines.
The memory 402 may be used to store the computer readable instructions, and the processor 401 may implement various functions of the message pushing device 400 by executing or executing the computer readable instructions or modules stored in the memory 402 and invoking data stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to the use of the message pushing device 400, and the like. In addition, the Memory 402 may include a hard disk, a Memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Memory Card (Flash Card), at least one disk storage device, a Flash Memory device, a Read-Only Memory (ROM), a Random Access Memory (RAM), or other non-volatile/volatile storage devices.
The integrated modules of the message pushing device 400 can be stored in a computer readable storage medium if they are implemented in the form of software functional modules and sold or used as independent products. Based on such understanding, all or part of the flow of the method according to the above embodiments may be implemented by hardware that is configured to be instructed by computer readable instructions, which may be stored in a computer readable storage medium, and when the computer readable instructions are executed by a processor, the steps of the method embodiments may be implemented.
Example 4
The present embodiment provides a computer-readable storage medium having stored thereon a computer program; the computer program is executed by a processor to implement the message push method in other embodiments.
The message pushing equipment and the storage medium in the embodiment of the application are adopted, and at least one message template is configured according to configuration requirements; receiving a push request, and adjusting a push message structure of a message template according to the push request; generating a push message according to the adjusted push message structure, and sending the push message to a push terminal; and after the push message is sent, recording the push record, and detecting the push state of whether the push message is successfully pushed. The method realizes simple and quick message pushing, is compatible with the participation and the participation of the original function interface on the whole based on the Apollo configuration message pushing method, and realizes simple and quick message pushing on the basis that the previously applied service function is not influenced.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present invention. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such 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 intended to include such modifications and variations as well.
Claims (10)
1. A message pushing method is characterized by comprising the following steps:
configuring at least one message template according to configuration requirements;
receiving a push request, and adjusting a push message structure of the message template according to the push request;
generating a push message according to the adjusted push message structure, and sending the push message to a push terminal;
and after the push message is sent, recording a push record, and detecting a push state of whether the push message is successfully pushed.
2. The message pushing method according to claim 1, wherein the configuring at least one message template according to the configuration requirement specifically includes:
and configuring the number of the message template, the message title, the message body field, the jump target URL and/or the message additional field which need to jump when the message is clicked according to the configuration requirement.
3. The message pushing method according to claim 2, wherein before receiving the pushing request and adjusting the pushing message structure of the message template according to the pushing request, the method further comprises performing request preprocessing according to the pushing request; the preprocessing of the request according to the push request specifically comprises the following steps:
presetting black and white lists of a pushing party and black and white lists of a pushing terminal;
after receiving a pushing request of a pushing party, acquiring an access password of the pushing party through access interception, and verifying the access password;
after the access password passes the verification, acquiring the identity ID of the pushing party, and comparing the identity ID with a black list and a white list of the pushing party; if the identity ID of the pushing party exists in a white list of the pushing party or the identity ID of the pushing party does not exist in a black list of the pushing party, the pushing party has the authority of pushing messages;
acquiring a user ID of a push terminal to be pushed by a push party, and comparing the user ID with a black list and a white list of the push terminal; and if the user ID of the push terminal exists in a white list of the push terminal or the user ID of the push terminal does not exist in a black list of the push terminal, the push terminal has the authority of receiving the push message.
4. The message pushing method according to claim 1, wherein before the message content of the message template is called and a push message is sent to a push terminal, the method further comprises:
and determining the type of the push terminal, selecting corresponding push service according to the type of the push terminal, and pushing the message.
5. The message pushing method according to claim 1, wherein after the push record is recorded after the push message is sent out, and a push state that whether the push message is successfully pushed is detected, the method further comprises: if the pushing state is pushing failure, acquiring a message receiving time period of the pushing terminal, and pushing the pushing message again in the corresponding time period, specifically comprising the following steps:
acquiring a message receiving time period of the push terminal;
setting the second message pushing time according to the message receiving time period, and timing;
and when the second message pushing time is reached, pushing the message to the pushing terminal again.
6. The message pushing method according to claim 1, wherein after the push record is recorded after the push message is sent out, and a push state that whether the push message is successfully pushed is detected, the method further comprises: the method comprises the following steps of establishing a mapping relation among configuration requirements, message templates and a push terminal in advance:
acquiring configuration requirements of a configuration party, wherein the configuration requirements comprise message titles, message body fields and/or message additional fields;
the configuration requirements, the message templates and the push terminals are in one-to-one correspondence, and a mapping relation is established;
and when receiving a new configuration requirement, determining a message template and a push terminal corresponding to the configuration requirement according to the established mapping relation.
7. A message push system is characterized by specifically comprising:
a template configuration module: the message template is used for configuring at least one message template according to configuration requirements;
a message adjusting module: the message template pushing device is used for receiving a pushing request and adjusting a pushing message structure of the message template according to the pushing request;
the message pushing module: the push message structure is used for generating a push message according to the adjusted push message structure and sending the push message to a push terminal;
a push feedback module: and the push state is used for recording a push record after the push message is sent out and detecting whether the push message is successfully pushed or not.
8. The message pushing system according to claim 7, wherein the template configuration module configures at least one message template according to a configuration requirement, specifically comprising:
and configuring the number of the message template, the message title, the message body field, the jump target URL and/or the message additional field which need to jump when the message is clicked according to the configuration requirement.
9. A message push device, comprising:
a memory: for storing executable instructions; and
a processor for interfacing with the memory to execute the executable instructions to perform the message pushing method of any of claims 1-6.
10. A computer-readable storage medium, having stored thereon a computer program; computer program to be executed by a processor for implementing a message push method as claimed in any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110268280.4A CN113239297A (en) | 2021-03-12 | 2021-03-12 | Message pushing method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110268280.4A CN113239297A (en) | 2021-03-12 | 2021-03-12 | Message pushing method, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113239297A true CN113239297A (en) | 2021-08-10 |
Family
ID=77130214
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110268280.4A Pending CN113239297A (en) | 2021-03-12 | 2021-03-12 | Message pushing method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113239297A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114448968A (en) * | 2021-12-15 | 2022-05-06 | 广州市玄武无线科技股份有限公司 | Pushed amount checking method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107465759A (en) * | 2017-09-07 | 2017-12-12 | 武汉楚鼎信息技术有限公司 | A kind of message server, message issuing method and terminal |
| CN107645524A (en) * | 2016-07-21 | 2018-01-30 | 腾讯科技（深圳）有限公司 | A kind of message push processing method and device |
| CN108768837A (en) * | 2018-05-31 | 2018-11-06 | 中国建设银行股份有限公司 | Message treatment method and relevant apparatus |
| CN110149363A (en) * | 2019-04-15 | 2019-08-20 | 深圳壹账通智能科技有限公司 | A kind of information push method, device and storage medium |
| CN110519711A (en) * | 2019-06-26 | 2019-11-29 | 中国移动通信集团江西有限公司 | A kind of information push method, device, storage medium and server |
-
2021
- 2021-03-12 CN CN202110268280.4A patent/CN113239297A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107645524A (en) * | 2016-07-21 | 2018-01-30 | 腾讯科技（深圳）有限公司 | A kind of message push processing method and device |
| CN107465759A (en) * | 2017-09-07 | 2017-12-12 | 武汉楚鼎信息技术有限公司 | A kind of message server, message issuing method and terminal |
| CN108768837A (en) * | 2018-05-31 | 2018-11-06 | 中国建设银行股份有限公司 | Message treatment method and relevant apparatus |
| CN110149363A (en) * | 2019-04-15 | 2019-08-20 | 深圳壹账通智能科技有限公司 | A kind of information push method, device and storage medium |
| CN110519711A (en) * | 2019-06-26 | 2019-11-29 | 中国移动通信集团江西有限公司 | A kind of information push method, device, storage medium and server |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114448968A (en) * | 2021-12-15 | 2022-05-06 | 广州市玄武无线科技股份有限公司 | Pushed amount checking method and device, electronic equipment and storage medium |
| CN114448968B (en) * | 2021-12-15 | 2023-01-10 | 广州市玄武无线科技股份有限公司 | Pushed amount checking method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7796742B1 (en) | Systems and methods for simplified provisioning | |
| CN109814856B (en) | Data entry method, device, terminal and computer readable storage medium | |
| CN102752326B (en) | The method of deal with data, server and system in the time of download file | |
| US10467066B2 (en) | System and method for establishing common request processing | |
| CN101305555B (en) | Multimedia middleware apparatus using metadata, method for controlling multimedia middleware | |
| CN110413528B (en) | Intelligent configuration method and system for test environment | |
| US20210312086A1 (en) | Apparatus and method for recommending user privacy control | |
| CN113076502A (en) | Parameter control method and system based on request identification | |
| CN106649638B (en) | Big data acquisition method | |
| CN112615753A (en) | Link abnormity tracking method, first node, second node and link | |
| CN107861765B (en) | Product configuration method, apparatus, and computer-readable storage medium | |
| CN113239297A (en) | Message pushing method, system and storage medium | |
| CN113485952A (en) | Data batch transmission method and device | |
| CN112559124A (en) | Model management system and target operation instruction processing method and device | |
| CN112507668A (en) | Project data storage certificate method, storage certificate system, terminal equipment and readable storage medium | |
| CN112116339A (en) | Capital full link control verification method and device | |
| CN112132671A (en) | Invoice information acquisition method and device, computer equipment and storage medium | |
| CN111464618A (en) | Message pushing method, device, equipment and storage medium | |
| CN109343880B (en) | RN packet updating method and device and readable storage medium | |
| CN105141586A (en) | Method and system for verifying user | |
| CN113347033B (en) | Root cause positioning method and system based on block chain and verification node | |
| WO2017143931A1 (en) | Method and apparatus for identifying smart card, method and apparatus for processing smart card identification data, and device | |
| CN101534317B (en) | Server, mobile phone terminal and method and system for acquiring mobile phone terminal number | |
| KR102107454B1 (en) | System for multiplication of financial payment networks, method for financial services using the same and computer program for the same | |
| CN113535558A (en) | Software version transmission method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |