CN105763584A - Message processing method and apparatus - Google Patents
Message processing method and apparatus Download PDFInfo
- Publication number
- CN105763584A CN105763584A CN201410788687.XA CN201410788687A CN105763584A CN 105763584 A CN105763584 A CN 105763584A CN 201410788687 A CN201410788687 A CN 201410788687A CN 105763584 A CN105763584 A CN 105763584A
- Authority
- CN
- China
- Prior art keywords
- message
- software platform
- extension software
- normal structure
- treat
- 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
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a message processing method and an apparatus. The method comprises the steps of acquiring the content of a message from a message editing platform; according to a predefined message standard structure, generating a standard structure message containing the content of the message; according to the predefined message standard structure and the mapping relationship of a message structure applicable to each promotion platform, parsing the standard structure message and converting the standard structure message into a to-be-pushed message applicable to a corresponding promotion platform, wherein the to-be-pushed message contains the content of the message; sending the to-be-pushed message to the corresponding promotion platform and then pushing the to-be-pushed message to user terminals through the promotion platform. According to the technical scheme of the message processing method and the apparatus, a user having the promotion requirement can push a message containing the same content to user terminals via multiple promotion platforms through editing the message only once via the message editing platform. Therefore, the pushing efficiency is improved.
Description
Technical field
The present invention relates to technical field of computer information processing, particularly relate to a kind of message treatment method and device.
Background technology
Along with popularizing of Internet technology, market occurs in that the substantial amounts of Extension Software Platform with message push function, such as immediate communication platform, shopping platform or promotion platform etc..Usual each Extension Software Platform is safeguarded by its development company, is respectively adopted different interface, agreement and message structure.Such user is when the message using different Extension Software Platform to push identical content, it is necessary to carry out the editor of message on each Extension Software Platform respectively, and the efficiency of the message so causing pushing identical contents by different Extension Software Platforms is very low.A such as food and beverage enterprise, is want the up-to-date food product being publicized oneself by the Extension Software Platform of more than three, then needs to safeguard respectively on every platform propaganda materials, it is necessary to do repeated work, cause that the efficiency of PUSH message is very low.
Summary of the invention
Based on this, it is necessary to for the technical problem that the efficiency of the message being pushed identical content at present by different Extension Software Platforms is very low, it is provided that a kind of message treatment method and device.
A kind of message treatment method, described method includes:
Message content is obtained from message editing platform；
The normal structure message of described message content is included according to predefined message criteria structural generation；
Mapping relations according to the message structure that predefined message criteria structure and each Extension Software Platform are suitable for, resolve described normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message；Described treat that PUSH message includes described message content；
Treat that PUSH message is sent to its corresponding Extension Software Platform by described, to treat that PUSH message is pushed to user terminal by this Extension Software Platform by described.
A kind of message processing apparatus, described device includes:
Message Processing center module, for obtaining message content from message editing platform；It is additionally operable to include the normal structure message of described message content according to predefined message criteria structural generation；
Message adaptation management module, the mapping relations of the message structure for being suitable for according to predefined message criteria structure and each Extension Software Platform, resolve described normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message；Described treat that PUSH message includes described message content；It is additionally operable to treat that PUSH message is sent to its corresponding Extension Software Platform by described, to treat that PUSH message is pushed to user terminal by this Extension Software Platform by described.
Above-mentioned message treatment method and device, when user is after message content is carried out disposable editor by message editing platform unification, just can automatically obtain message content and generate normal structure message, resolve to change into again and treat PUSH message suitable in each Extension Software Platform, what will convert into treats that PUSH message is pushed to the Extension Software Platform being suitable for corresponding message structure so that Extension Software Platform will treat that PUSH message is finally pushed to corresponding user terminal again.So have the user of popularization demand only need on message editing platform once property editor, just can realize pushing the message with identical message content to user terminal by multiple Extension Software Platforms, improve pushing efficiency.And it is more many to push required Extension Software Platform, during PUSH message, efficiency raising is more obvious.
Accompanying drawing explanation
Fig. 1 is for implementing the applied environment figure of the message processing server of message treatment method in an embodiment；
Fig. 2 is the schematic flow sheet of message treatment method in an embodiment；
Fig. 3 is the schematic flow sheet of the step transmitting user message in an embodiment；
Fig. 4 is the schematic flow sheet of message treatment method in another embodiment；
Fig. 5 is the schematic flow sheet of message treatment method in further embodiment；
Fig. 6 is the schematic flow sheet of message treatment method in an embodiment；
Fig. 7 continues request when asking unsuccessfully in one embodiment, request is stopped when asking the frequency of failure to reach request frequency of failure threshold value, and the normal structure message currently extracted is aligned to the tail of the queue of normal structure message queue, and the normal structure message continuing to extract current head of the queue from normal structure message queue carries out the detailed step schematic flow sheet that processes；
Fig. 8 is the structured flowchart of message processing apparatus in an embodiment；
Fig. 9 is the structured flowchart of message processing apparatus in another embodiment；
Figure 10 is the applied environment figure of message processing apparatus in an embodiment.
Detailed description of the invention
In order to make the purpose of the present invention, technical scheme and advantage clearly understand, below in conjunction with drawings and Examples, the present invention is further elaborated.Should be appreciated that specific embodiment described herein is only in order to explain the present invention, is not intended to limit the present invention.
As shown in Figure 1, in one embodiment, provide a kind of message processing server, this message processing server is connected by network with message editing platform and multiple Extension Software Platform (first, second and the 3rd Extension Software Platform in Fig. 1) respectively, and each Extension Software Platform can be connected to corresponding user terminal when needed.User terminal (the first and second user terminal in Fig. 1) can pass through to run promote corresponding with certain Extension Software Platform and support should be used for realizing its support to corresponding Extension Software Platform push function.Such as first user terminal is run simultaneously and has the first popularization support application and second to promote support application, wherein first promote support application corresponding to the first Extension Software Platform, second promotes support application corresponding to the second Extension Software Platform, then first user terminal can receive the first Extension Software Platform and the message of the second Extension Software Platform propelling movement.Here popularization support application can be instant messaging application, shopping application, pay application or game application etc..
As in figure 2 it is shown, in one embodiment, it is provided that a kind of message treatment method, the message processing server that the present embodiment is applied to as shown in Figure 1 in this way illustrates.The method specifically includes following steps:
Step 202, obtains message content from message editing platform.
Specifically, message editing platform is mainly used in providing the editting function for message content, and concrete message editing platform can provide message editing interface, receives the message content of user's typing with popularization demand.Here message content includes but not limited at least one in text message and multimedia messages, and wherein multimedia messages includes but not limited at least one in video information, audio-frequency information and picture.User's message content of typing on message editing platform is stored in data base.Message processing server timing can obtain message content from message editing platform.
In one embodiment, message processing server can also obtain at least one the propelling movement object information corresponding with message content and propelling movement side's information from message editing platform.Wherein corresponding with message content propelling movement object information is the information of the recipient that this message content is final after this message content of propelling movement.Push object information can include pushing object identity and/or pushing characteristics of objects information, push object identity and refer to and push the mark of the recipient that this message content is final after this message content.Push the mark that object identity can be one group of customer group with common trait, the group number in such as instant messaging.Push the characteristic that the recipient that after characteristics of objects information then refers to this message content of propelling movement, this message content is final possesses, the such as information such as age bracket, sex and user location.Propelling movement side's information then refers to the information of a side providing this message content, the information such as such as its name, title, account, the pet name.
Step 204, includes the normal structure message of message content according to predefined message criteria structural generation.
Specifically, predefined message criteria structure refers to the unified structure of the message that message processing server this locality adopts, it is possible to including message format and project label, the normal structure message of generation then also includes the entry value corresponding to project label.Wherein message format includes but not limited to JSON form, XML format or YAML form.Wherein JSON full name is JavaScriptObjectNotation, is the data interchange format of a kind of lightweight；XML full name is ExtensibleMarkupLanguage, is a kind of make it have structural markup language for labelling e-file；YAML full name is YetAnotherMarkupLanguage, is another kind of markup language.
Illustrating, according to JSON form, then certain normal structure message can be expressed as follows:
Wherein " ToUser " pushes object information mark, " FromUser " is propelling movement side's message identification, and " CreateTime " is message creation time mark, and " MsgType " is message content types mark, " Content " is message content mark, and " MessageId " is message identification code mark.Pushing object identity, propelling movement side's mark, establishment time marking, message content types mark, message content mark and message identification code mark is all project label, and its each self-corresponding value respectively pushes object information, propelling movement side's information, message creation time, message content types, message content and message identification code, these values are the entry value of respective item mark.
Step 206, the mapping relations according to the message structure that predefined message criteria structure and each Extension Software Platform are suitable for, resolve normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message；Treat that PUSH message includes message content.
Specifically, for each Extension Software Platform in some Extension Software Platforms of determining, set up predefined message criteria structure respectively and the mapping relations of message structure that this Extension Software Platform is suitable for.The message structure that certain Extension Software Platform is suitable for refers to the message structure that the message that this Extension Software Platform pushes is supported.Treat that PUSH message at least includes message content, can also include when necessary pushing the information such as object information, propelling movement side's information, message creation time, message content types, message content and message identification code.
In one embodiment, the mapping relations of the message structure that predefined message criteria structure and each Extension Software Platform are suitable for, the message structure being suitable for including predefined message criteria structure and each Extension Software Platform mapping relations between message format, cipher mode, project label and entry value option respectively.Here cipher mode includes the mode arbitrarily can message being encrypted, such as AES encryption mode, rsa encryption mode and des encryption mode etc., and wherein AES full name is AdvancedEncryptionStandard, means Advanced Encryption Standard；RSA is a kind of public key data encryption standard；DES full name is DataEncryptionStandard, i.e. data encryption standards, is a kind of block algorithm using key to encrypt.Its project label adopted of different message structures is different, it is possible to project label is mapped.Entry value option refers to the value of the fixed range that some project label is corresponding, and such as message content types generally includes text type mark and picture/mb-type mark, it is possible to these entry value options are mapped.
Illustrating, the mapping relations of the message structure that predefined message criteria structure and each Extension Software Platform are suitable for can be as shown in Table 1:
When resolving normal structure message, according to corresponding message format, resolve each project label and entry value thereof one by one and change, if than the message that normal structure message from " Li Si " in the example above need to be converted to the message structure that the second Extension Software Platform is suitable for, then can according to table one, convert JSON form to XML format, " Content " is converted to " Fcontent ", " text " is converted to " T ", and adopt rsa encryption mode to encrypt it, just obtain have the second platform be suitable for message structure treat PUSH message.
In one embodiment, step 206 specifically includes: by corresponding respectively to the message adapter of each Extension Software Platform, with the mapping relations of the message structure that the Extension Software Platform corresponding to predefined message criteria structure and this message adapter is suitable for, resolve normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message.
Specifically, in the present embodiment, corresponding different Extension Software Platform is respectively configured and each Extension Software Platform message adapter one to one, corresponding first message adapter of such as the first Extension Software Platform, corresponding second message adapter of the second Extension Software Platform, by that analogy.Each message adapter has expresses predefined message criteria structure and the function of the mapping relations of message structure that the Extension Software Platform corresponding to this message adapter is suitable for, it is possible to by this message adapter normal structure message resolved and converts to there is the applicable message structure of corresponding Extension Software Platform treat PUSH message.In the present embodiment, resolve according to mapping relations and be converted into certain Extension Software Platform until PUSH message time, it is possible to directly invoke the message adapter corresponding with Extension Software Platform and generate and treat PUSH message.Often increase a new Extension Software Platform, it is only necessary to one message adapter of corresponding configuration just can complete again；In like manner, cancelling an existing Extension Software Platform only needs to cancel the message adapter of its correspondence, and easy to maintenance, maintenance cost is low.
Step 208, will treat that PUSH message is sent to its corresponding Extension Software Platform, will treat that PUSH message is pushed to user terminal by this Extension Software Platform.
Specifically, message processing server adopts the communication protocol of each self-supporting of each Extension Software Platform, will treat that PUSH message is pushed to the Extension Software Platform that the message structure treating PUSH message with this is corresponding.What such as the above-mentioned message structure being suitable for according to the second Extension Software Platform changed into treats PUSH message from " Li Si ", will be pushed to the second Extension Software Platform.Extension Software Platform has corresponding with this Extension Software Platform user terminal promoted and support application receiving to be pushed to again through its push channel to run after PUSH message.Extension Software Platform can treat PUSH message according to subscriber identification broadcasts all on it, it is also possible to pushes this according to the propelling movement object information orientation treated in PUSH message and treats PUSH message.
In one embodiment, step 208 specifically includes: obtain the communicated tokens of Extension Software Platform corresponding with the breath structure treating PUSH message, and according to this to corresponding Extension Software Platform requests verification authority；After verifying authorization passes through, adopt communication protocol that corresponding Extension Software Platform supports will treat that PUSH message is sent to its corresponding Extension Software Platform, will treat that PUSH message is pushed to user terminal by this Extension Software Platform.
In the present embodiment, message processing server safeguards an authentication service module, propelling movement until PUSH message time, the communicated tokens (TOKEN) of the Extension Software Platform mandate corresponding with treating PUSH message is obtained by calling this authentication service module, use this communicated tokens to corresponding Extension Software Platform requests verification authority, just can pass through this Extension Software Platform after being verified and will treat that PUSH message is pushed to user terminal.The communication protocol suitable in this Extension Software Platform can be adopted when being pushed to Extension Software Platform.By safeguarding that communicated tokens realizes the support to Extension Software Platform safety verification demand in the present embodiment.
Above-mentioned message treatment method and, when user is after message content is carried out disposable editor by message editing platform unification, just can automatically obtain message content and generate normal structure message, resolve to change into again and treat PUSH message suitable in each Extension Software Platform, what will convert into treats that PUSH message is pushed to the Extension Software Platform being suitable for corresponding message structure so that Extension Software Platform will treat that PUSH message is finally pushed to corresponding user terminal again.So have the user of popularization demand only need on message editing platform once property editor, just can realize pushing the message with identical message content to user terminal by multiple Extension Software Platforms, improve pushing efficiency.And it is more many to push required Extension Software Platform, during PUSH message, efficiency raising is more obvious.
As it is shown on figure 3, in one embodiment, this message treatment method also includes the step of transmission user message, specifically includes following steps:
Step 302, receives the user message that user terminal is sent by its corresponding Extension Software Platform.
Specifically, by promoting of running on it, user terminal supports that application sends user message to the Extension Software Platform that this application is corresponding, message processing server then gets this user message from this Extension Software Platform.This user message has the message structure being suitable for corresponding Extension Software Platform.
Step 304, the message structure being suitable for according to the Extension Software Platform sending user message and the mapping relations of predefined message criteria structure, resolve user message to convert the user message of predefined message criteria structure to.
Specifically, message processing server calls the message adapter corresponding with the Extension Software Platform sending user message, the message structure being suitable for according to its expressed corresponding Extension Software Platform and the mapping relations of predefined message criteria structure, resolve user message and convert the user message of predefined message criteria structure to.
In one embodiment, it is possible to user message is formed pending user message queue, from pending user message queue, extracts the user message of current head of the queue one by one.Then the message structure being suitable for according to the Extension Software Platform sending user message and the mapping relations of predefined message criteria structure, resolve the user message currently extracted to convert the user message of predefined message criteria structure to.
Step 306, is sent to message editing platform by the user message of predefined message criteria structure.
Specifically, the user message of predefined message criteria structure is sent to message editing platform, it is achieved there is the messaging interaction between user and the message recipient of popularization demand.
In the present embodiment, message processing server can obtain message content from message editing platform, and thereby through multiple Extension Software Platforms to user terminal PUSH message, and message recipient can also send message by each self-corresponding Extension Software Platform to message editing platform.So have between user and the message recipient of popularization demand can two-way interaction, meet two-way communication demand.
As shown in Figure 4, in one embodiment, it is provided that a kind of message treatment method, the present embodiment still message processing server being applied in this way as shown in Figure 1 illustrates.The method specifically includes following steps:
Step 402, obtains message content from message editing platform.
Step 404, includes the normal structure message of message content according to predefined message criteria structural generation.
Step 406, forms normal structure message queue by normal structure message.
Specifically, the sequencing generated according to normal structure message forms normal structure message queue.Each normal structure message has message identification code, it is possible to represents corresponding normal structure message by message identification code and forms the queue of a first in first out, is called normal structure message queue.
Step 408, extracts the normal structure message of current head of the queue one by one from normal structure message queue.
According to the principle of first in first out, extracting the normal structure message of current head of the queue in this queue from normal structure message queue one by one, the normal structure message that this extracts no longer is aligned to the head of the queue of normal structure message queue.The normal structure message extracted gets sending permission.
Step 410, the mapping relations according to the message structure that predefined message criteria structure and each Extension Software Platform are suitable for, resolve the normal structure message currently extracted with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message；Treat that PUSH message includes message content.
Step 412, will treat that PUSH message is sent to its corresponding Extension Software Platform, will treat that PUSH message is pushed to user terminal by this Extension Software Platform.
In the present embodiment, normal structure message is formed normal structure message queue and processes, it is ensured that normal structure message can be processed in an orderly manner, it is prevented that cause message blocking because processing substantial amounts of message, lose or repeat to send.
As it is shown in figure 5, in one embodiment, it is provided that a kind of message treatment method, the present embodiment still message processing server being applied in this way as shown in Figure 1 illustrates.The method specifically includes following steps:
Step 502, obtains message content from message editing platform.
With reference to Fig. 6, message processing server obtains message content to create promotion message from message editing platform.
Step 504, includes the normal structure message of message content according to predefined message criteria structural generation.
With reference to Fig. 6, message processing server can call Message Processing center module and promotion message is carried out Message Processing, and to include the normal structure message of message content according to predefined message criteria structural generation, what generate in concrete Fig. 6 is JSON structured message.
Step 506, forms normal structure message queue by normal structure message.
Step 508, extracts the normal structure message of current head of the queue one by one from normal structure message queue.
With reference to Fig. 6, from normal structure message queue, extract the normal structure message of current head of the queue so that the normal structure message that this extracts obtains sending permission.
Step 510, it is judged that whether the normal structure message currently extracted is repeating transmission.If then performing step 512, then perform step 514 if not.
Specifically, judge that whether the normal structure message currently extracted be that repeating transmission can be passed through to judge whether it extracts first from normal structure message queue and judges, if extracting from normal structure message queue first, not retransmit, if not extracting first, being retransmit.Here repeating transmission refers to not send and successfully and again sends, and sends and is successfully not sent further on.
Step 512, what direct acquisition had stored treats PUSH message corresponding to the normal structure message currently extracted.
Step 514, mapping relations according to the message structure that predefined message criteria structure and each Extension Software Platform are suitable for, resolve the normal structure message currently extracted with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message, store treat PUSH message corresponding to the normal structure message currently extracted；Treat that PUSH message includes message content.
Specifically, the normal structure message extracted is if not retransmitting, and but without carrying out parsing and the process of conversion before explanation, now performs step 514 and treats that PUSH message is to carry out follow-up process to obtain, and this being treated, PUSH message stores.Here storage can be cached in internal memory, it is also possible to is that storage is in data base.
If the normal structure message extracted is to retransmit, had be carried out before explanation resolving and the process of conversion, now can directly obtain the treating PUSH message and carrying out follow-up process corresponding to the normal structure message currently extracted stored.
Step 516, sends this to Extension Software Platform corresponding with treating PUSH message request and treats PUSH message.Perform step 518 when asking successfully, perform step 520 when asking unsuccessfully.
Specifically, can setting waiting time, if sending this to Extension Software Platform corresponding with treating PUSH message request to treat PUSH message, this Extension Software Platform exceedes waiting time and does not respond to, then decision request failure.Here waiting time could be arranged to 10 seconds.
Step 518, will treat that PUSH message is sent to its corresponding Extension Software Platform, will treat that PUSH message is pushed to user terminal by this Extension Software Platform.
Step 520, continue request, stop asking when asking the frequency of failure to reach request frequency of failure threshold value, and the normal structure message currently extracted is aligned to the tail of the queue of normal structure message queue, and the normal structure message continuing to extract current head of the queue from normal structure message queue processes.
Specifically, request frequency of failure threshold value is numerical value set in advance, it is possible to be set to 2, if so the request frequency of failure reaches 2 times just to stop asking, and corresponding normal structure message is aligned to the tail of the queue of normal structure message queue.Then proceeding to perform above-mentioned steps 508, the normal structure message to continue to extract current head of the queue from normal structure message queue processes.
In the present embodiment, by judging whether the normal structure message extracted is repeating transmission, thus directly obtain when being judged as YES stored treat PUSH message, so can save server resource and improve treatment effeciency.Furthermore, each normal structure message extracted repeatedly asks to send, it is possible to ensure that message can be sent to as far as possible；And request is stopped when asking the frequency of failure to reach request frequency of failure threshold value, now show because some reason treats that PUSH message cannot be pushed to corresponding Extension Software Platform, then temporarily it is aligned to tail of the queue and continues with the next one and treat PUSH message, taken into account reliability and the efficiency of propelling movement.
As it is shown in fig. 7, in one embodiment, step 520 specifically includes following steps:
Step 702, continues request when asking unsuccessfully, stops request when asking the frequency of failure to reach request frequency of failure threshold value and judges that the normal structure message currently extracted sends unsuccessfully.
When performing step 510, if the normal structure message currently extracted exists sends failed record, then it represents that it is for retransmitting.The normal structure message that can correspond to currently extract arranges flag bit, and initial value is 0, if it is determined that the normal structure message currently extracted sends unsuccessfully then flag bit adds 1.
Step 704, the accumulative transmission frequency of failure of the normal structure message that detection is currently extracted and the size sending frequency of failure threshold value.If the accumulative frequency of failure that sends is less than sending frequency of failure threshold value, perform step 706, otherwise perform step 708.
Specifically, sending frequency of failure threshold value is value set in advance, it is possible to be set as 3.The value of the flag bit that can obtain the normal structure message corresponding to currently extracting adds up to send the frequency of failure as it, compares size with sending frequency of failure threshold value 3.
Step 706, is aligned to the tail of the queue of normal structure message queue by the normal structure message currently extracted, and the normal structure message continuing to extract current head of the queue from normal structure message queue processes.
Specifically, if the accumulative transmission frequency of failure of the normal structure message currently extracted is but without reaching to send frequency of failure threshold value, then next time also can extract it and process.
Step 708, abandons the normal structure message currently extracted, and the normal structure message continuing to extract current head of the queue from normal structure message queue processes.
Specifically, if the accumulative transmission frequency of failure of the normal structure message currently extracted has reached transmission frequency of failure threshold value, can be determined that this treats that PUSH message cannot be sent to, now the normal structure message currently extracted is rejected from normal structure message queue, and create the message failed notice of transmission and feed back to message editing platform.So there is message push the user of demand and receive this notice, it is possible to according to be analyzed, search and send failed reason.
In the present embodiment, by suitably abandoning the normal structure message that cannot be sent to, it is to avoid normal structure message queue is long, it is ensured that the efficiency of propelling movement also saves server resource.
As shown in Figure 8, in one embodiment, it is provided that a kind of message processing apparatus 800, there is the function of the message treatment method realizing each embodiment above-mentioned.This message processing apparatus 800 includes: Message Processing center module 802 and message adaptation management module 804.
Message Processing center module 802, for obtaining message content from message editing platform；It is additionally operable to include the normal structure message of message content according to predefined message criteria structural generation.
Message adaptation management module 804, the mapping relations of the message structure for being suitable for according to predefined message criteria structure and each Extension Software Platform, resolve normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message；Treat that PUSH message includes message content；It is additionally operable to treat that PUSH message is sent to its corresponding Extension Software Platform, will treat that PUSH message is pushed to user terminal by this Extension Software Platform.
In one embodiment, message adaptation management module 804 is additionally operable to receive the user message that user terminal is sent by its corresponding Extension Software Platform；The message structure being suitable for according to the Extension Software Platform sending user message and the mapping relations of predefined message criteria structure, resolve user message to convert the user message of predefined message criteria structure to.And Message Processing center module 802 is additionally operable to the user message of predefined message criteria structure is sent to message editing platform.
As it is shown in figure 9, in one embodiment, this message processing apparatus 800 also includes queue management module 803, and with reference to the applied environment figure of message processing apparatus 800 as shown in Figure 10.Queue management module 803 is for forming normal structure message queue by normal structure message；The normal structure message of current head of the queue is extracted one by one from normal structure message queue.And message adaptation management module 804 is additionally operable to the mapping relations of the message structure being suitable for according to predefined message criteria structure and each Extension Software Platform, resolve the normal structure message currently extracted with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message.
In one embodiment, message adaptation management module 804 is additionally operable to send this to Extension Software Platform corresponding with treating PUSH message request and treats PUSH message.When asking successfully, will treat that PUSH message is sent to its corresponding Extension Software Platform, will treat that PUSH message is pushed to user terminal by this Extension Software Platform.Request is continued when asking unsuccessfully, request is stopped when asking the frequency of failure to reach request frequency of failure threshold value, and the normal structure message currently extracted is aligned to the tail of the queue of normal structure message queue, and the normal structure message continuing to extract current head of the queue from normal structure message queue processes.
In one embodiment, queue management module 803 be additionally operable to resolve normal structure message with convert to have message structure that corresponding Extension Software Platform is suitable for treat PUSH message after, store treat PUSH message corresponding to the normal structure message currently extracted.And message adaptation management module 804 is additionally operable to judge whether the normal structure message currently extracted is repeating transmission.Be additionally operable to if it is determined that be retransmit, then directly acquisition stored treat PUSH message corresponding to the normal structure message currently extracted.If it is determined that be not retransmit, then the mapping relations of the message structure being suitable for according to predefined message criteria structure and each Extension Software Platform, resolve the normal structure message currently extracted with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message.
In one embodiment, message adaptation management module 804 is additionally operable to continue request when asking unsuccessfully, stops request when asking the frequency of failure to reach request frequency of failure threshold value and judges that the normal structure message currently extracted sends unsuccessfully.It is additionally operable to the accumulative transmission frequency of failure detecting the normal structure message currently extracted and the size sending frequency of failure threshold value.If being additionally operable to the accumulative frequency of failure that sends less than transmission frequency of failure threshold value, then the normal structure message currently extracted is aligned to the tail of the queue of normal structure message queue, and the normal structure message continuing to extract current head of the queue from normal structure message queue processes.If being additionally operable to the accumulative frequency of failure that sends more than or equal to transmission frequency of failure threshold value, then abandon the normal structure message currently extracted, and the normal structure message continuing to extract current head of the queue from normal structure message queue processes.
In one embodiment, message adaptation management module 804 is additionally operable to the message adapter by corresponding respectively to each Extension Software Platform, with the mapping relations of the message structure that the Extension Software Platform corresponding to predefined message criteria structure and this message adapter is suitable for, resolve normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message.
In one embodiment, message adaptation management module 804 is additionally operable to obtain the communicated tokens of Extension Software Platform corresponding with the breath structure treating PUSH message, and according to this to corresponding Extension Software Platform requests verification authority.It is additionally operable to after verifying authorization passes through, adopts communication protocol that corresponding Extension Software Platform supports will treat that PUSH message is sent to its corresponding Extension Software Platform, will treat that PUSH message is pushed to user terminal by this Extension Software Platform.
In one embodiment, the mapping relations of the message structure that predefined message criteria structure and each Extension Software Platform are suitable for, the message structure being suitable for including predefined message criteria structure and each Extension Software Platform mapping relations between message format, cipher mode, project label and entry value option respectively.
Embodiment described above only have expressed the several embodiments of the present invention, and it describes comparatively concrete and detailed, but therefore can not be interpreted as the restriction to the scope of the claims of the present invention.It should be pointed out that, for the person of ordinary skill of the art, without departing from the inventive concept of the premise, it is also possible to making some deformation and improvement, these broadly fall into protection scope of the present invention.Therefore, the protection domain of patent of the present invention should be as the criterion with claims.
Claims (10)
1. a message treatment method, described method includes:
Message content is obtained from message editing platform；
The normal structure message of described message content is included according to predefined message criteria structural generation；
Mapping relations according to the message structure that predefined message criteria structure and each Extension Software Platform are suitable for, resolve described normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message；Described treat that PUSH message includes described message content；
Treat that PUSH message is sent to its corresponding Extension Software Platform by described, to treat that PUSH message is pushed to user terminal by this Extension Software Platform by described.
2. method according to claim 1, it is characterised in that described method also includes:
Receive the user message that described user terminal is sent by its corresponding Extension Software Platform；
The message structure being suitable for according to the Extension Software Platform sending described user message and the mapping relations of predefined message criteria structure, resolve described user message to convert the user message of predefined message criteria structure to；
The user message of described predefined message criteria structure is sent to described message editing platform.
3. method according to claim 1, it is characterized in that, the mapping relations of the message structure that the predefined message criteria structure of described basis and each Extension Software Platform are suitable for, resolve described normal structure message with convert to have corresponding Extension Software Platform be suitable for message structure treat PUSH message before, also include:
Described normal structure message is formed normal structure message queue；
The normal structure message of current head of the queue is extracted one by one from described normal structure message queue；
The mapping relations of the message structure that the predefined message criteria structure of described basis and each Extension Software Platform are suitable for, resolve described normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message, including:
Mapping relations according to the message structure that predefined message criteria structure and each Extension Software Platform are suitable for, resolve the normal structure message currently extracted with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message.
4. method according to claim 3, it is characterised in that described treat that PUSH message is sent to its corresponding Extension Software Platform by described, to treat that PUSH message is pushed to user terminal by this Extension Software Platform by described, including:
Treat that the request of PUSH message corresponding Extension Software Platform sends this and treats PUSH message to described；
When asking successfully, treat that PUSH message is sent to its corresponding Extension Software Platform by described, to treat that PUSH message is pushed to user terminal by this Extension Software Platform by described；
Request is continued when asking unsuccessfully, request is stopped when asking the frequency of failure to reach request frequency of failure threshold value, and the normal structure message currently extracted is aligned to the tail of the queue of described normal structure message queue, and the normal structure message continuing to extract current head of the queue from described normal structure message queue processes.
5. method according to claim 4, it is characterised in that described parsing described normal structure message with convert to have corresponding Extension Software Platform be suitable for message structure treat PUSH message after, also include:
PUSH message is treated described in storing corresponding to the normal structure message currently extracted；
After the described normal structure message extracting current head of the queue one by one from described normal structure message queue, also include:
Judge whether the normal structure message currently extracted is repeating transmission；
If retransmitting, then directly acquisition stored treat PUSH message corresponding to the normal structure message currently extracted；
If not retransmitting, then perform the predefined message criteria structure of described basis and the mapping relations of message structure that each Extension Software Platform is suitable for, resolve the normal structure message currently extracted to convert the step treating PUSH message with the message structure that corresponding Extension Software Platform is suitable for.
6. method according to claim 4, it is characterized in that, described continuation when asking unsuccessfully is asked, request is stopped when asking the frequency of failure to reach request frequency of failure threshold value, and the normal structure message currently extracted is aligned to the tail of the queue of described normal structure message queue, and the normal structure message continuing to extract current head of the queue from described normal structure message queue processes, including:
Continue request when asking unsuccessfully, stop request when asking the frequency of failure to reach request frequency of failure threshold value and judge that the normal structure message currently extracted sends unsuccessfully；
The accumulative transmission frequency of failure of the normal structure message that detection is currently extracted and the size sending frequency of failure threshold value；
If the described accumulative transmission frequency of failure is less than described transmission frequency of failure threshold value, then the normal structure message currently extracted is aligned to the tail of the queue of described normal structure message queue, and the normal structure message continuing to extract current head of the queue from described normal structure message queue processes；
If the described accumulative transmission frequency of failure is more than or equal to described transmission frequency of failure threshold value, then abandon the normal structure message currently extracted, and the normal structure message continuing to extract current head of the queue from described normal structure message queue processes.
7. method according to claim 1, it is characterized in that, the mapping relations of the message structure that the predefined message criteria structure of described basis and each Extension Software Platform are suitable for, resolve described normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message, including:
By corresponding respectively to the message adapter of each Extension Software Platform, with the mapping relations of the message structure that the Extension Software Platform corresponding to predefined message criteria structure and this message adapter is suitable for, resolve described normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message.
8. method according to claim 1, it is characterised in that described treat that PUSH message is sent to its corresponding Extension Software Platform by described, to treat that PUSH message is pushed to user terminal by this Extension Software Platform by described, including:
Obtain the communicated tokens of Extension Software Platform corresponding with the described breath structure treating PUSH message, and according to this to corresponding Extension Software Platform requests verification authority；
After verifying authorization passes through, communication protocol that corresponding Extension Software Platform supports is adopted to treat that PUSH message is sent to its corresponding Extension Software Platform by described, to treat that PUSH message is pushed to user terminal by this Extension Software Platform by described.
9. method according to claim 1, it is characterized in that, the mapping relations of the message structure that described predefined message criteria structure and each Extension Software Platform are suitable for, the message structure being suitable for including predefined message criteria structure and each Extension Software Platform mapping relations between message format, cipher mode, project label and entry value option respectively.
10. a message processing apparatus, it is characterised in that described device includes:
Message Processing center module, for obtaining message content from message editing platform；It is additionally operable to include the normal structure message of described message content according to predefined message criteria structural generation；
Message adaptation management module, the mapping relations of the message structure for being suitable for according to predefined message criteria structure and each Extension Software Platform, resolve described normal structure message with convert to there is message structure that corresponding Extension Software Platform is suitable for treat PUSH message；Described treat that PUSH message includes described message content；It is additionally operable to treat that PUSH message is sent to its corresponding Extension Software Platform by described, to treat that PUSH message is pushed to user terminal by this Extension Software Platform by described.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410788687.XA CN105763584A (en) | 2014-12-17 | 2014-12-17 | Message processing method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410788687.XA CN105763584A (en) | 2014-12-17 | 2014-12-17 | Message processing method and apparatus |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105763584A true CN105763584A (en) | 2016-07-13 |
Family
ID=56339545
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410788687.XA Pending CN105763584A (en) | 2014-12-17 | 2014-12-17 | Message processing method and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105763584A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115454671A (en) * | 2022-09-07 | 2022-12-09 | 中国建设银行股份有限公司 | Message processing method, device, equipment and storage medium |
| CN115988069A (en) * | 2022-12-27 | 2023-04-18 | 中科云谷科技有限公司 | Data pushing method and device and computer storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101001212A (en) * | 2006-01-12 | 2007-07-18 | 鸿富锦精密工业（深圳）有限公司 | Multisystem message interaction managing and control system and method |
| CN101957755A (en) * | 2010-09-21 | 2011-01-26 | 用友软件股份有限公司 | Method and device for uniformly managing message |
| WO2014035194A1 (en) * | 2012-08-30 | 2014-03-06 | Samsung Electronics Co., Ltd. | Push message service system and method |
| CN103970603A (en) * | 2014-05-21 | 2014-08-06 | 哈尔滨工程大学 | Task scheduling method of event injection engine based on multilevel feedback queue |
| CN103973461A (en) * | 2013-02-06 | 2014-08-06 | 阿里巴巴集团控股有限公司 | Notification message pushing method and message server |
-
2014
- 2014-12-17 CN CN201410788687.XA patent/CN105763584A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101001212A (en) * | 2006-01-12 | 2007-07-18 | 鸿富锦精密工业（深圳）有限公司 | Multisystem message interaction managing and control system and method |
| CN101957755A (en) * | 2010-09-21 | 2011-01-26 | 用友软件股份有限公司 | Method and device for uniformly managing message |
| WO2014035194A1 (en) * | 2012-08-30 | 2014-03-06 | Samsung Electronics Co., Ltd. | Push message service system and method |
| CN103973461A (en) * | 2013-02-06 | 2014-08-06 | 阿里巴巴集团控股有限公司 | Notification message pushing method and message server |
| CN103970603A (en) * | 2014-05-21 | 2014-08-06 | 哈尔滨工程大学 | Task scheduling method of event injection engine based on multilevel feedback queue |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115454671A (en) * | 2022-09-07 | 2022-12-09 | 中国建设银行股份有限公司 | Message processing method, device, equipment and storage medium |
| CN115988069A (en) * | 2022-12-27 | 2023-04-18 | 中科云谷科技有限公司 | Data pushing method and device and computer storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101299753B (en) | Web service security control mechanism based on proxy server | |
| CN102904865B (en) | A kind of management method, system and equipment of the multiple digital certificates based on mobile terminal | |
| CN108243188B (en) | Interface access, interface call and interface verification processing method and device | |
| TW201545526A (en) | Method, apparatus, and system for providing a security check | |
| CN105515941B (en) | A kind of method and system of message and recovery under wechat development mode | |
| CN105303714B (en) | A kind of method of barcode scanning pickup | |
| CN107801165A (en) | Service note method for pushing, device, computer equipment and storage medium | |
| KR20130040471A (en) | Apparus and method for authorizing combining code using quick response code | |
| US10447796B2 (en) | Pushlet instant messaging framework and pushlet instant messaging method | |
| CN105025480B (en) | The method and system of subscriber card digital signature authentication | |
| CN110061995A (en) | A kind of mouse, identity authorization system, method, apparatus and storage medium | |
| CN106685937B (en) | Customized internet television http protocol method based on Netty packaging | |
| US20130179503A1 (en) | Event notification system for associating an outgoing electronic message with an incoming response | |
| US10833762B2 (en) | Information transmission method, information reception method and apparatus | |
| CN104579657A (en) | Method and device for identity authentication | |
| CN103888348B (en) | E-mail applications system and electron post transmission method, device | |
| CN113542274A (en) | Cross-domain data transmission method, device, server and storage medium | |
| KR102294918B1 (en) | System and method for automatic selection of message transmission channels and deduplication of messages based on multiple blockchains | |
| CN105763584A (en) | Message processing method and apparatus | |
| KR100842868B1 (en) | Spam short message blocking system using call back short message and spam short message blocking method using the same | |
| US20080268883A1 (en) | Spam short message blocking system using a call back short message and a method thereof | |
| CN106713224B (en) | Document authority control method | |
| KR102072134B1 (en) | Message transmission apparatus, message server and message receipt appratus | |
| CN105430623A (en) | Monitoring method, device and system for RCS junk message | |
| CN110650014B (en) | Signature authentication method, system, equipment and storage medium based on hessian protocol |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160713 |
|
| RJ01 | Rejection of invention patent application after publication |