CN105677402A - Message transforming method and device - Google Patents
Message transforming method and device Download PDFInfo
- Publication number
- CN105677402A CN105677402A CN201511031322.3A CN201511031322A CN105677402A CN 105677402 A CN105677402 A CN 105677402A CN 201511031322 A CN201511031322 A CN 201511031322A CN 105677402 A CN105677402 A CN 105677402A
- Authority
- CN
- China
- Prior art keywords
- message
- assembly
- type
- software version
- file
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
Abstract
The embodiment of the invention discloses a message transforming method and device. The method includes the steps that a first message sent by a first assembly to a second assembly is acquired; the software version of the first assembly and the software version of the second assembly are recognized, wherein the software version of the first assembly is different from the software version of the second assembly; a first message type description file conforming to the software version of the first assembly and a second message type description file conforming to the software version of the second assembly are called so as to determine message change information; the message type of the first message is changed according to the message change information, and a changed message type is obtained; a second message is generated according to the changed message type. Due to the fact that the second message type description file is needed as a basis for the process of generating the second message, the second message can be recognized and processed by the second assembly, then the assemblies in different software versions can understand messages transmitted to each other, and thus normal working of a system can be maintained in the software upgrading process.
Description
Technical field
The present invention relates to data processing field, particularly relate to a kind of message conversion method and device.
Background technology
Software release upgrade is the conventional means that systems soft ware realizes content update, for larger system such as distributed system, system can include substantial amounts of assembly (English: Component), assembly is provided with software, when software version needs to upgrade, if the software of all component in system to be carried out software release upgrade simultaneously simultaneously, the black account phase that system cannot work for a long time can be caused. Therefore generally, for larger system, what take is the mode that assembly progressively carries out software upgrading, for instance the software version of a part of assembly of first upgrading, then updates the mode of the software version of a part of assembly.
Assembly in system is progressively carried out in the process of software upgrading, the situation that the software version between assembly differs can be caused in system. In escalation process, system is still working on, and there is the mutual of message between the assembly of system, if occurring interacting message between the assembly of different software versions, can cause mutual None-identified between assembly, understanding the message that opposite end is sent. Such as system includes assembly a and assembly b, in software upgrade process, version n has been arrived in the software release upgrade of assembly a, version m has been arrived in the software release upgrade of assembly b, if now assembly a receives the assembly b message 1 sent, owing between assembly a and b, software version is different, assembly a is likely to None-identified, understands message 1 is any message, contain any content, thus cannot produce the assembly b message 1 sent to respond or process message 1. Thus the normal operation that the system that have impact on is in software upgrade process.
Visible, allow between the assembly under different software versions it will be appreciated that the message sent mutually is one needs badly and solve the technical problem that.
Summary of the invention
In order to solve above-mentioned technical problem, the invention provides a kind of message conversion method and device, it is achieved it will be appreciated that the message sent mutually between the assembly under different software versions so that described system can keep normal operation in software upgrade process.
The embodiment of the invention discloses following technical scheme:
A kind of message conversion method, is applied to include in the system of multiple assembly, and described method includes:
Obtain the first message that the first assembly sends, described first assembly and the assembly that the second assembly is described system to the second assembly;
Identifying the software version of described first assembly and the second assembly, the software version of described first assembly is different from the software version of described second assembly;
Transferring the first type of message that the software version with described first assembly is consistent and describe file, the second type of message being consistent with the software version of described second assembly describes file;
Describe file identification according to described first type of message and go out the type of message of described first message;
Describe file according to described first type of message, described second type of message describes the type of message of file and described first message and determines message alteration information, and described message alteration information is for identifying the difference relative to described first message under the software version of described first assembly of described first message under the software version of described second assembly;
The type of message of described first message, the type of message after being changed is revised according to described message alteration information;
Generate the second message with the type of message after described change, and send described second message to described second assembly.
Optionally, described generate the second message with the type of message after described change, including:
Judge that message space shared by the type of message after described change is whether more than message space shared by the type of message of described first message;
If more than, solicitation message space meets the empty message of message space shared by the type of message after described change, generates described second message according to the type of message after described empty message and described change;
If being not more than, generate described second message according to the type of message after described first message and described change.
Optionally, also include:
Obtain the source code of each software version in described system in advance;
Automatically the type of message of each software version is identified by software code compilation process;
Type of message according to each software version extracted generates and describes file with software version type of message one to one, including first type of message corresponding with the software version of described first assembly describe file and with described the and the second type of message corresponding to the software version of assembly describes file.
Optionally, the software version of described identification the first assembly and the second assembly, including:
The software version of the first assembly and the second assembly according to as offered procedure identification; Or,
The software version of the first assembly and the second assembly according to the interactive information identification between described first assembly and the second assembly.
Optionally, the message space that the type of message of described first message includes message name, type, message member Name, message member type, the message member side-play amount in described first message, message member takes up room and the type of message of described first message takies.
A kind of message conversion device, is applied to include in the system of multiple assembly, and described device includes:
First acquiring unit, for obtaining the first message that the first assembly sends, described first assembly and the assembly that the second assembly is described system to the second assembly;
First recognition unit, for identifying the software version of described first assembly and the second assembly, the software version of described first assembly is different from the software version of described second assembly;
Transferring unit, the first type of message being consistent for transferring the software version with described first assembly describes file, and the second type of message being consistent with the software version of described second assembly describes file;
Second recognition unit, goes out the type of message of described first message for describing file identification according to described first type of message;
Determine unit, for describing file according to described first type of message, described second type of message describe the type of message of file and described first message and determine message alteration information, described message alteration information is for identifying the difference relative to described first message under the software version of described first assembly of described first message under the software version of described second assembly;
Amendment unit, for revising the type of message of described first message, the type of message after being changed according to described message alteration information;
First generates unit, for generating the second message with the type of message after described change, and sends described second message to described second assembly.
Optionally,
Described first generates unit specifically for judging that message space shared by the type of message after described change is whether more than message space shared by the type of message of described first message;
If more than, solicitation message space meets the empty message of message space shared by the type of message after described change, generates described second message according to the type of message after described empty message and described change;
If being not more than, generate described second message according to the type of message after described first message and described change.
Optionally, also include:
Second acquisition unit, for obtaining the source code of each software version in described system in advance;
Compilation unit, for automatically identifying the type of message of each software version by software code compilation process;
Second generates unit generates according to the type of message of each software version extracted and describes file with software version type of message one to one, including first type of message corresponding with the software version of described first assembly describe file and with described the and the second type of message corresponding to the software version of assembly describes file.
Optionally,
Described first recognition unit is specifically for the software version of the first assembly and the second assembly according to as offered procedure identification; Or,
Described first recognition unit is specifically for the software version of the first assembly and the second assembly according to the interactive information identification between described first assembly and the second assembly.
Optionally, the message space that the type of message of described first message includes message name, type, message member Name, message member type, the message member side-play amount in described first message, message member takes up room and the type of message of described first message takies.
Be can be seen that by technique scheme, obtain the first message that the first assembly sends to the second assembly, identify the first assembly and the software version of the second assembly, the software version of described first assembly is different from the software version of described second assembly, transfer the first type of message that the software version with described first assembly is consistent and describe file, the second type of message being consistent with the software version of described second assembly describes file, according to described first type of message, file is described, described second type of message describes file and the type of message of described first message identified determines message alteration information, the type of message of described first message is revised according to described message alteration information, type of message after being changed, the second message is generated with the type of message after described change, process owing to generating the second message needs to describe file according to described second type of message, therefore described second message can by described second component recognition and process, thus can realize between the assembly under different software versions it will be appreciated that the message that sends mutually, make described system can keep normal operation in software upgrade process.
Accompanying drawing explanation
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, the accompanying drawing used required in embodiment or description of the prior art will be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the premise not paying creative work, it is also possible to obtain other accompanying drawing according to these accompanying drawings.
The method flow diagram of a kind of message conversion method that Fig. 1 provides for the embodiment of the present invention;
A kind of type of message that previously generates that Fig. 2 provides for the embodiment of the present invention describes the method flow diagram of document method;
The structure drawing of device of a kind of message conversion device that Fig. 3 provides for the embodiment of the present invention.
Detailed description of the invention
For making the purpose of the embodiment of the present invention, technical scheme and advantage clearly, below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is explicitly described, it is clear that, described embodiment is a part of embodiment of the present invention, rather than whole embodiments. Based on the embodiment in the present invention, the every other embodiment that those of ordinary skill in the art obtain under not making creative work premise, broadly fall into the scope of protection of the invention.
Including substantial amounts of assembly in large-scale system, when redaction occurs in the software of assembly, the software version in the assembly that self is included that described system can be in good time is upgraded accordingly. System can be caused great burden by all component simultaneously updating software release, cause system cannot normal operation, not there is feasibility.
Therefore generally, for larger system, what take is the mode that assembly progressively carries out software upgrading, for instance the software version of a part of assembly of first upgrading, then updates the mode of the software version of a part of assembly. This to system in assembly progressively carry out in the process of software upgrading, can cause in system that situation about differing occurs in the software version between assembly. In escalation process, system is still working on, it is possible that message mutual between the assembly of system, if interacting message occurring between the assembly of different software versions, mutual None-identified between assembly can be caused, understand the message that opposite end is sent, thus the normal operation that the system that have impact on is in software upgrade process. Visible, allow between the assembly under different software versions it will be appreciated that the message sent mutually is one needs badly and solve the technical problem that.
Inventors have discovered that a kind of traditional message conversion regime, in conventional manner, the mode adopting h coding obtains message transcode, such as with the form of converter.c, for changing the message format between the assembly of different software versions, assembly a from the assembly b of such as software version n to software version m send message 1 time, message transcode by corresponding software version n to software version m, message 1 is converted to the understandable form of software version m, such assembly a will may identify which and effectively process message 1, the no longer normal operation of influential system.
But, the message transcode limitation of this h coding is very big, and a message transcode is only used for from specific software version n to software version m the conversion of message format, once software version variation, it is necessary to again write coding. In system, the software version quantity of software is various, and along with the iteration of software is issued, the message transcode quantity for different software versions situation will get more and more, it is difficult to safeguard. And the artificial experience influence of process of h coding is bigger, it is easy to make mistakes, cause message transcode to convert power to not high.
For this, embodiments provide a kind of message conversion method and device, obtain the first message that the first assembly sends to the second assembly, identify the first assembly and the software version of the second assembly, the software version of described first assembly is different from the software version of described second assembly, transfer the first type of message that the software version with described first assembly is consistent and describe file, the second type of message being consistent with the software version of described second assembly describes file, according to described first type of message, file is described, described second type of message describes file and the type of message of described first message identified determines message alteration information, the type of message of described first message is revised according to described message alteration information, type of message after being changed, the second message is generated with the type of message after described change, process owing to generating the second message needs to describe file according to described second type of message, therefore described second message can by described second component recognition and process, thus can realize between the assembly under different software versions it will be appreciated that the message that sends mutually, make described system can keep normal operation in software upgrade process.
The method flow diagram of a kind of message conversion method that Fig. 1 provides for the embodiment of the present invention, is applied to include in the system of multiple assembly, and described method includes:
101: obtain the first message that the first assembly sends, described first assembly and the assembly that the second assembly is described system to the second assembly.
Illustrate, it is possible to before described second assembly receives described first message, obtain described first message. In concrete application scenarios, can in the process carrying out software release upgrade, the receiving port front end of each assembly in the system, message format conversion equipment is set, obtained described first message by message format conversion equipment prior to the assembly as receiving terminal, and described first message is processed. Described message format conversion equipment be a kind of have message under certain software version is converted to the device of message type under another software version.
102: identify the software version of described first assembly and the second assembly, the software version of described first assembly is different from the software version of described second assembly.
Illustrate, in embodiments of the present invention, the front end message receiver (MessageFrontierReceiver) being arranged on before described second assembly receiving terminal can be passed through and realize identifying the software version of the first assembly and the second assembly, and whether coupling is identical. Generally, described front end message receiver can get described first message prior to described message format conversion equipment.
Optionally, the mode of the software version of at least two recognizer component is embodiments provided. First kind of way, it is possible to by the mode of as offered, determines that in as offered process concrete software version information distinguished by described first assembly and the second assembly. Or, the second way, it is possible to the software version of the first assembly and the second assembly according to the interactive information identification between described first assembly and the second assembly. Interactive information between described first assembly and the second assembly can carry the software version information that sender is concrete, such as, the information that described first assembly sends to the second assembly can be carried the software version of described first assembly, the information that described second assembly sends to the first assembly can be carried the software version of described second assembly.
By identifying the software version of described first assembly and the second assembly, it can be determined that identify that whether the software version of the software version of described first assembly and the second assembly is identical. Present invention is generally directed to the message conversion between the assembly that software version is different, if the software version of two assemblies is identical, then the problem not havinging message None-identified.
It should be noted that the software version of described first assembly can be higher than the software version of described second assembly, the software version of described first assembly can also be lower than the software version of described second assembly. This is not construed as limiting by the present invention.
103: transferring the first type of message that the software version with described first assembly is consistent and describe file, the second type of message being consistent with the software version of described second assembly describes file.
Illustrate, type of message describes file and pre-sets, for a software version, have one one to one type of message file is described. It is not refer in particular to the type of message corresponding to some software version to describe file that described first type of message describes file, and corresponds to the software version of described first assembly.Assume that the software version of described first assembly is that version 2 is (English: Version, abbreviation: v), described first type of message describes the type of message that file is corresponding v2 and describes file, the software version update assuming described first assembly is v3, then described first type of message describes file and the type of message for corresponding v3 is described file. In like manner, described second type of message describes the file software version corresponding to described second assembly.
Optionally, embodiments provide and a kind of previously generate the method that type of message describes file, as in figure 2 it is shown, described method includes:
201: obtain the source code of each software version in described system in advance.
Illustrating, described source code can be the source code running on the system program in establishment. In general, software version has the source code of a set of correspondence.
202: automatically identified the type of message of each software version by software code compilation process.
Illustrate, message format extractor automatization can be passed through in embodiments of the present invention and extract the type of message in software source code. The function of described message format extractor can be realized by compiler plug-in unit, for instance, it is possible to use compiler plug-in unit typeparse.so automatically identifies type of message in the compilation process to software source code and extracts described type of message. Each software version has the type of message of correspondence.
Described type of message is (English: MessageType) can to include message name (English: objectname), type is (English: objecttype), message member Name is (English: itemname), message member type is (English: itemtype), message member side-play amount in described first message is (English: offset), message member takes up room (English: bytes) and the message space (English: total_size) that takies of the type of message of described first message.
203: generate according to the type of message of each software version extracted and describe file with software version type of message one to one, including first type of message corresponding with the software version of described first assembly describe file and with described the and the second type of message corresponding to the software version of assembly describes file.
Illustrating, it can be a kind of source binary code that described type of message describes file. Can being such as the form of .xml, the type of message of corresponding software version n describes file can called after version_n.xml. Described type of message describes file and includes the content of type of message various piece.
The source code of each software version of software all can be transferred in advance, describes the mode of file by previously generating and preserve described type of message, it is possible to calls according to concrete software version when there being message conversion requirements. Eliminate and traditional approach it is frequently necessary to h coding again, improve efficiency.
104: describe file identification according to described first type of message and go out the type of message of described first message.
105: describe file according to described first type of message, described second type of message describes the type of message of file and described first message and determines message alteration information, and described message alteration information is for identifying the difference relative to described first message under the software version of described first assembly of described first message under the software version of described second assembly.
Illustrate, describe file by described first type of message and may identify which the information of each message member in the type of message of described first message. Describe file by the first type of message described in comparison and described second type of message describes file, it is possible to clearly described first message is in the software version of described first assembly and the difference under the software version of described second assembly. Described message alteration information can be the software version relative to described first assembly, and whether which described first message has distinguish under the software version of described second assembly, for instance increase or decrease some message member etc.
106: revise the type of message of described first message, the type of message after being changed according to described message alteration information.
107: generate the second message with the type of message after described change, and send described second message to described second assembly.
Illustrate, if described message alteration information is for adding a message member a3, the type of message of described first message is " a1:1, a2:2 ", the type of message " a1:1; a2:2; a3:0 " after being changed, say, that the type of message of described second message is " a1:1; a2:2, a3:0 ". By adding a3 field, and to compose default value be 0, under not changing the premise of flesh and blood of described first message so that described second assembly may identify which and process described second message.
It should be noted that when described first message is changed, the size of message space shared by the type of message after the described change obtained after conversion may with the varying in size of message space shared by the type of message of described first message. In the embodiment of the present invention, it is possible to the different size of message space shared by the type of message after described change, process accordingly in the process generating described second message.
Optionally, described generate the second message with the type of message after described change, including:
Judge that message space shared by the type of message after described change is whether more than message space shared by the type of message of described first message.
If more than, solicitation message space meets the empty message of message space shared by the type of message after described change, generates described second message according to the type of message after described empty message and described change.
If being not more than, generate described second message according to the type of message after described first message and described change.
Illustrating, if message space shared by the type of message after described change is more than message space shared by the type of message of described first message, described first message will not be sufficient to for carrying the type of message after described change. At this moment need again one message of application to carry the type of message after described change, for instance can to the new message of internal memory application. The message space shared by empty message of application is more than message space shared by the type of message after described change, it is sufficient to carries the type of message after described change, is filled in empty message by the type of message after stating change, obtains described second message.
If message space shared by the type of message after described change is less than or equal to message space shared by the type of message of described first message, described first message can be used, type of message after described change is replaced the type of message of described first message, obtains described second message.
As can be seen from the above-described embodiment, obtain the first message that the first assembly sends to the second assembly, identify the first assembly and the software version of the second assembly, the software version of described first assembly is different from the software version of described second assembly, transfer the first type of message that the software version with described first assembly is consistent and describe file, the second type of message being consistent with the software version of described second assembly describes file, according to described first type of message, file is described, described second type of message describes file and the type of message of described first message identified determines message alteration information, the type of message of described first message is revised according to described message alteration information, type of message after being changed, the second message is generated with the type of message after described change, process owing to generating the second message needs to describe file according to described second type of message, therefore described second message can by described second component recognition and process, thus can realize between the assembly under different software versions it will be appreciated that the message that sends mutually, make described system can keep normal operation in software upgrade process.
The structure drawing of device of a kind of message conversion device that Fig. 3 provides for the embodiment of the present invention, is applied to include in the system of multiple assembly, and described message conversion device 300 includes:
First acquiring unit 301, for obtaining the first message that the first assembly sends, described first assembly and the assembly that the second assembly is described system to the second assembly;
First recognition unit 302, for identifying the software version of described first assembly and the second assembly, the software version of described first assembly is different from the software version of described second assembly;
Transferring unit 303, the first type of message being consistent for transferring the software version with described first assembly describes file, and the second type of message being consistent with the software version of described second assembly describes file;
Second recognition unit 304, goes out the type of message of described first message for describing file identification according to described first type of message;
Determine unit 305, for describing file according to described first type of message, described second type of message describe the type of message of file and described first message and determine message alteration information, described message alteration information is for identifying the difference relative to described first message under the software version of described first assembly of described first message under the software version of described second assembly;
Amendment unit 306, for revising the type of message of described first message, the type of message after being changed according to described message alteration information;
First generates unit 307, for generating the second message with the type of message after described change, and sends described second message to described second assembly.
Optionally,
Described first generates unit specifically for judging that message space shared by the type of message after described change is whether more than message space shared by the type of message of described first message;
If more than, solicitation message space meets the empty message of message space shared by the type of message after described change, generates described second message according to the type of message after described empty message and described change;
If being not more than, generate described second message according to the type of message after described first message and described change.
Optionally, also include:
Second acquisition unit, for obtaining the source code of each software version in described system in advance;
Compilation unit, for automatically identifying the type of message of each software version by software code compilation process;
Second generates unit generates according to the type of message of each software version extracted and describes file with software version type of message one to one, including first type of message corresponding with the software version of described first assembly describe file and with described the and the second type of message corresponding to the software version of assembly describes file.
Optionally,
Described first recognition unit is specifically for the software version of the first assembly and the second assembly according to as offered procedure identification; Or,
Described first recognition unit is specifically for the software version of the first assembly and the second assembly according to the interactive information identification between described first assembly and the second assembly.
Optionally, the message space that the type of message of described first message includes message name, type, message member Name, message member type, the message member side-play amount in described first message, message member takes up room and the type of message of described first message takies.
As can be seen from the above-described embodiment, obtain the first message that the first assembly sends to the second assembly, identify the first assembly and the software version of the second assembly, the software version of described first assembly is different from the software version of described second assembly, transfer the first type of message that the software version with described first assembly is consistent and describe file, the second type of message being consistent with the software version of described second assembly describes file, according to described first type of message, file is described, described second type of message describes file and the type of message of described first message identified determines message alteration information, the type of message of described first message is revised according to described message alteration information, type of message after being changed, the second message is generated with the type of message after described change, process owing to generating the second message needs to describe file according to described second type of message, therefore described second message can by described second component recognition and process, thus can realize between the assembly under different software versions it will be appreciated that the message that sends mutually, make described system can keep normal operation in software upgrade process.
One of ordinary skill in the art will appreciate that: all or part of step realizing said method embodiment can be completed by the hardware that programmed instruction is relevant, foregoing routine can be stored in a computer read/write memory medium, this program upon execution, performs to include the step of said method embodiment; And aforesaid storage medium can be at least one in following medium: read only memory (English: read-onlymemory, ROM), the various media that can store program code such as RAM, magnetic disc or CD abbreviation:.
It should be noted that each embodiment in this specification all adopts the mode gone forward one by one to describe, between each embodiment identical similar part mutually referring to, what each embodiment stressed is the difference with other embodiments. Especially for equipment and system embodiment, owing to it is substantially similar to embodiment of the method, so describing fairly simple, relevant part illustrates referring to the part of embodiment of the method. Equipment described above and system embodiment are merely schematic, the unit wherein illustrated as separating component can be or may not be physically separate, the parts shown as unit can be or may not be physical location, namely may be located at a place, or can also be distributed on multiple NE. Some or all of module therein can be selected according to the actual needs to realize the purpose of the present embodiment scheme. Those of ordinary skill in the art, when not paying creative work, are namely appreciated that and implement.
The above; being only the present invention preferably detailed description of the invention, but protection scope of the present invention is not limited thereto, any those familiar with the art is in the technical scope that the invention discloses; the change that can readily occur in or replacement, all should be encompassed within protection scope of the present invention. Therefore, protection scope of the present invention should be as the criterion with scope of the claims.
Claims (10)
1. a message conversion method, it is characterised in that being applied to include in the system of multiple assembly, described method includes:
Obtain the first message that the first assembly sends, described first assembly and the assembly that the second assembly is described system to the second assembly;
Identifying the software version of described first assembly and the second assembly, the software version of described first assembly is different from the software version of described second assembly;
Transferring the first type of message that the software version with described first assembly is consistent and describe file, the second type of message being consistent with the software version of described second assembly describes file;
Describe file identification according to described first type of message and go out the type of message of described first message;
Describe file according to described first type of message, described second type of message describes the type of message of file and described first message and determines message alteration information, and described message alteration information is for identifying the difference relative to described first message under the software version of described first assembly of described first message under the software version of described second assembly;
The type of message of described first message, the type of message after being changed is revised according to described message alteration information;
Generate the second message with the type of message after described change, and send described second message to described second assembly.
2. method according to claim 1, it is characterised in that described generate the second message with the type of message after described change, including:
Judge that message space shared by the type of message after described change is whether more than message space shared by the type of message of described first message;
If more than, solicitation message space meets the empty message of message space shared by the type of message after described change, generates described second message according to the type of message after described empty message and described change;
If being not more than, generate described second message according to the type of message after described first message and described change.
3. method according to claim 1, it is characterised in that also include:
Obtain the source code of each software version in described system in advance;
Automatically the type of message of each software version is identified by software code compilation process;
Type of message according to each software version extracted generates and describes file with software version type of message one to one, including first type of message corresponding with the software version of described first assembly describe file and with described the and the second type of message corresponding to the software version of assembly describes file.
4. method according to claim 1, it is characterised in that the software version of described identification the first assembly and the second assembly, including:
The software version of the first assembly and the second assembly according to as offered procedure identification; Or,
The software version of the first assembly and the second assembly according to the interactive information identification between described first assembly and the second assembly.
5. the method according to any one of Claims 1-4, it is characterized in that, the message space that the type of message of described first message includes message name, type, message member Name, message member type, the message member side-play amount in described first message, message member takes up room and the type of message of described first message takies.
6. a message conversion device, it is characterised in that being applied to include in the system of multiple assembly, described device includes:
First acquiring unit, for obtaining the first message that the first assembly sends, described first assembly and the assembly that the second assembly is described system to the second assembly;
First recognition unit, for identifying the software version of described first assembly and the second assembly, the software version of described first assembly is different from the software version of described second assembly;
Transferring unit, the first type of message being consistent for transferring the software version with described first assembly describes file, and the second type of message being consistent with the software version of described second assembly describes file;
Second recognition unit, goes out the type of message of described first message for describing file identification according to described first type of message;
Determine unit, for describing file according to described first type of message, described second type of message describe the type of message of file and described first message and determine message alteration information, described message alteration information is for identifying the difference relative to described first message under the software version of described first assembly of described first message under the software version of described second assembly;
Amendment unit, for revising the type of message of described first message, the type of message after being changed according to described message alteration information;
First generates unit, for generating the second message with the type of message after described change, and sends described second message to described second assembly.
7. device according to claim 6, it is characterised in that
Described first generates unit specifically for judging that message space shared by the type of message after described change is whether more than message space shared by the type of message of described first message;
If more than, solicitation message space meets the empty message of message space shared by the type of message after described change, generates described second message according to the type of message after described empty message and described change;
If being not more than, generate described second message according to the type of message after described first message and described change.
8. device according to claim 6, it is characterised in that also include:
Second acquisition unit, for obtaining the source code of each software version in described system in advance;
Compilation unit, for automatically identifying the type of message of each software version by software code compilation process;
Second generates unit generates according to the type of message of each software version extracted and describes file with software version type of message one to one, including first type of message corresponding with the software version of described first assembly describe file and with described the and the second type of message corresponding to the software version of assembly describes file.
9. device according to claim 6, it is characterised in that
Described first recognition unit is specifically for the software version of the first assembly and the second assembly according to as offered procedure identification; Or,
Described first recognition unit is specifically for the software version of the first assembly and the second assembly according to the interactive information identification between described first assembly and the second assembly.
10. the device according to any one of claim 6 to 9, it is characterized in that, the message space that the type of message of described first message includes message name, type, message member Name, message member type, the message member side-play amount in described first message, message member takes up room and the type of message of described first message takies.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511031322.3A CN105677402B (en) | 2015-12-31 | 2015-12-31 | A kind of message conversion method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511031322.3A CN105677402B (en) | 2015-12-31 | 2015-12-31 | A kind of message conversion method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105677402A true CN105677402A (en) | 2016-06-15 |
| CN105677402B CN105677402B (en) | 2019-06-11 |
Family
ID=56298451
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201511031322.3A Active CN105677402B (en) | 2015-12-31 | 2015-12-31 | A kind of message conversion method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105677402B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1267415A (en) * | 1997-08-14 | 2000-09-20 | 诺基亚网络有限公司 | Centralized management of communication devices |
| CN1845535A (en) * | 2005-07-13 | 2006-10-11 | 华为技术有限公司 | Message matching method and system |
| US20060253540A1 (en) * | 1999-06-10 | 2006-11-09 | Ec Enabler, Ltd. (A New York Corporation) | Method and system for transferring information |
| CN101008894A (en) * | 2007-01-26 | 2007-08-01 | 华为技术有限公司 | Method and device for implementing compatibility between the old and new editions of system |
| CN101436126A (en) * | 2007-11-13 | 2009-05-20 | 华为技术有限公司 | Information translating method and device in on-line upgrading process |
| CN101505307A (en) * | 2009-03-09 | 2009-08-12 | 华为技术有限公司 | Message processing method, network node and system oriented to service architecture |
| CN101594355A (en) * | 2009-06-17 | 2009-12-02 | 华为技术有限公司 | A kind of method and device of realizing cross-version software interaction |
| US20110161929A1 (en) * | 2009-12-28 | 2011-06-30 | Jesse Keating | Using an enterprise messaging bus to automatically influence the process of software compilation and packaging for use by a collaborative project |
| CN102195895A (en) * | 2011-03-23 | 2011-09-21 | 中兴通讯股份有限公司 | Message sending and receiving processing method and device |
| CN102378293A (en) * | 2010-08-11 | 2012-03-14 | 中兴通讯股份有限公司 | Code division multiple access system and A17 interface compatibility realization method |
-
2015
- 2015-12-31 CN CN201511031322.3A patent/CN105677402B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1267415A (en) * | 1997-08-14 | 2000-09-20 | 诺基亚网络有限公司 | Centralized management of communication devices |
| US20060253540A1 (en) * | 1999-06-10 | 2006-11-09 | Ec Enabler, Ltd. (A New York Corporation) | Method and system for transferring information |
| CN1845535A (en) * | 2005-07-13 | 2006-10-11 | 华为技术有限公司 | Message matching method and system |
| CN101008894A (en) * | 2007-01-26 | 2007-08-01 | 华为技术有限公司 | Method and device for implementing compatibility between the old and new editions of system |
| CN101436126A (en) * | 2007-11-13 | 2009-05-20 | 华为技术有限公司 | Information translating method and device in on-line upgrading process |
| CN101505307A (en) * | 2009-03-09 | 2009-08-12 | 华为技术有限公司 | Message processing method, network node and system oriented to service architecture |
| CN101594355A (en) * | 2009-06-17 | 2009-12-02 | 华为技术有限公司 | A kind of method and device of realizing cross-version software interaction |
| US20110161929A1 (en) * | 2009-12-28 | 2011-06-30 | Jesse Keating | Using an enterprise messaging bus to automatically influence the process of software compilation and packaging for use by a collaborative project |
| CN102378293A (en) * | 2010-08-11 | 2012-03-14 | 中兴通讯股份有限公司 | Code division multiple access system and A17 interface compatibility realization method |
| CN102195895A (en) * | 2011-03-23 | 2011-09-21 | 中兴通讯股份有限公司 | Message sending and receiving processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105677402B (en) | 2019-06-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2273361B1 (en) | Method and system for updating versions of content stored in a storage device | |
| CN105590051B (en) | Trusted application for credible performing environment generates and installation method | |
| CN101594355B (en) | Method and device for realizing cross-version software interaction | |
| CN102779191B (en) | A kind of system that realizes of MySQL database smooth upgrade and implementation method | |
| KR20040022451A (en) | Embedded software update system | |
| CN102195895B (en) | Message sending and receiving processing method and device | |
| US11720420B2 (en) | Adaptive application version integration support | |
| CN105808278A (en) | Client version upgrading method and device | |
| CN102036055A (en) | Camera cradle head control system and control method | |
| CN106790347A (en) | A kind of large-scale concurrent data forwarding method based on netty | |
| CN105681343A (en) | Processing method and device for state control protocol based on ARM architecture | |
| CN106383726B (en) | A kind of signal adapter upgrade method based on image/video coffret | |
| CN105677402A (en) | Message transforming method and device | |
| CN104572212A (en) | Terminal updating system and updating method thereof | |
| CN110704528A (en) | Data processing method capable of automatic identification and configuration conversion | |
| CN112035135A (en) | Method, apparatus and storage medium for updating firmware program of slave station apparatus | |
| US20150248285A1 (en) | Method for adapting changes of operation environment and supporting upgrade and evolution of system and system thereof | |
| CN1838665A (en) | Adapting method between different byte sequence styles in network communication | |
| CN111142848A (en) | Software program compiling method, software program executing method and software program compiling device | |
| CN110928713B (en) | Database service fault repairing method, related device and storage medium | |
| CN108833526A (en) | A kind of intelligent gateway upgrade method | |
| CN109104623A (en) | A method of exempt to compile and unravels silk quick replacement boot LOGO | |
| CN105721550B (en) | A kind of fault-tolerant monitoring method of client and system | |
| CN114168165B (en) | Highly-integrated semi-automatic development method for sub-functions of Internet of things | |
| CN103502968A (en) | Generic data exchange method using hierarchical routing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |