CN110290127A - A message conversion method and message conversion system - Google Patents

Abstract

The present application provides a message conversion method and a message conversion system, the method comprising: receiving a first message sent by a first device; parsing the first message to obtain a target identification address; according to the target identification address, select a target protocol analysis plug-in from at least two protocol analysis plug-ins; use the target protocol analysis plug-in to convert the first message to obtain a second message; send the second message to the second device . In this way, after receiving the first message, the target protocol analysis plug-in can be selected from at least two protocol analysis plug-ins, and the first message can be converted by the target protocol analysis plug-in. There is no need to customize and develop different software systems for different smart devices, reducing the difficulty of message conversion, and the compatibility of the message conversion system is better.

Description

A message conversion method and message conversion system

technical field

The present application relates to the technical field of communications, and in particular to a message conversion method and a message conversion system.

Background technique

In the case of diversified power communication protocols, smart devices produced by different manufacturers and even different types of smart devices use different power communication protocols. These power communication protocols are not compatible, and smart devices connected to different power communication protocols need to customize and develop different software systems to communicate with the server. Even after the deployment is running, if the third-party interface changes, the developer needs to re-develop and deploy. Therefore, in the related art, since various power communication protocols are not compatible, different software systems need to be customized and developed for different smart devices, and message conversion is difficult.

Contents of the invention

The present application provides a message conversion method and a message conversion system to solve the problem of different software systems developed for different smart devices due to the incompatibility of various power communication protocols in related technologies. Difficult question.

On the one hand, the present application provides a message conversion method, including:

receiving a first message sent by the first device;

Analyzing the first packet to obtain a target identification address;

Select a target protocol analysis plug-in from at least two protocol analysis plug-ins according to the target identification address;

Converting the first message by using the target protocol parsing plug-in to obtain a second message;

Send the second message to a second device.

Optionally, the selecting a target protocol analysis plug-in from at least two protocol analysis plug-ins according to the target identification address includes:

Determine the target communication protocol according to the target identification address and the configuration file, wherein the configuration file includes the correspondence between the identification address and the communication protocol;

According to the target communication protocol, a target protocol parsing plug-in corresponding to the target communication protocol is selected from the at least two protocol parsing plug-ins.

Optionally, the receiving the first message sent by the first device includes:

receiving the first packet sent by the underlying device;

The step of using the target protocol parsing plug-in to convert the first message to obtain the second message includes:

Utilize the target specification analysis plug-in to convert the first message to obtain the second message in JavaScript Object Numbered Notation (JSON) format;

The sending the second message to the second device includes:

Send the second message in JSON format to the server.

Optionally, the receiving the first message sent by the first device includes:

Receive the first message in JSON format sent by the server;

The step of using the target protocol parsing plug-in to convert the first message to obtain the second message includes:

Converting the first message in the JSON format by using the target protocol parsing plug-in to obtain a second message in the protocol message format;

The sending the second message to the second device includes:

Send the second packet in the protocol packet format to the underlying device.

Optionally, the sending the second message in the protocol message format to the underlying device includes:

According to the target identification address, determine the underlying device with the target identification address;

Sending the second packet in the protocol packet format to the underlying device having the target identification address.

On the other hand, the present application also provides a message conversion system, including:

a receiving module, configured to receive the first message sent by the first device;

A parsing module, configured to parse the first message to obtain a target identification address;

A selection module, configured to select a target protocol analysis plug-in from at least two protocol analysis plug-ins according to the target identification address;

A conversion module, configured to use the target protocol parsing plug-in to convert the first message to obtain a second message;

A sending module, configured to send the second message to the second device.

Optionally, the selection module includes:

The first determining submodule is configured to determine the target communication protocol according to the target identification address and the configuration file, wherein the configuration file includes the correspondence between the identification address and the communication protocol;

The selection submodule is configured to select a target protocol parsing plug-in corresponding to the target communication protocol among the at least two protocol parsing plug-ins according to the target communication protocol.

Optionally, the receiving module is configured to receive the first packet sent by the underlying device;

The conversion module is used to convert the first message by using the target specification parsing plug-in to obtain the second message in JavaScript Object Numbered Notation (JSON) format;

The sending module is configured to send the second message in JSON format to the server.

Optionally, the receiving module is configured to receive the first message in JSON format sent by the server;

The conversion module is used to convert the first message in the JSON format by using the target protocol parsing plug-in to obtain the second message in the protocol message format;

The sending module is configured to send the second message in the protocol message format to the underlying device.

Optionally, the sending module includes:

The second determination submodule is configured to determine the underlying device with the target identification address according to the target identification address;

The sending submodule is configured to send the second message in the protocol message format to the underlying device having the target identification address.

It can be seen from the above technical solutions that the present application provides a message conversion method and a message conversion system, the method comprising: receiving a first message sent by a first device; parsing the first message to obtain a target identifier address; according to the target identification address, select a target protocol analysis plug-in from at least two protocol analysis plug-ins; use the target protocol analysis plug-in to convert the first message to obtain a second message; to the second device Send the second message. In this way, after receiving the first message, the target protocol analysis plug-in can be selected from at least two protocol analysis plug-ins, and the first message can be converted by the target protocol analysis plug-in. There is no need to customize and develop different software systems for different smart devices, reducing the difficulty of message conversion, and the compatibility of the message conversion system is better.

Description of drawings

In order to illustrate the technical solution of the present application more clearly, the accompanying drawings that need to be used in the embodiments will be briefly introduced below. Obviously, for those of ordinary skill in the art, on the premise of not paying creative work, there are also Additional figures can be derived from these figures.

Fig. 1 is a flow chart of a message conversion method provided by the present application;

Fig. 2 is a flowchart of another message conversion method provided by the present application;

Fig. 3 is a flowchart of another message conversion method provided by the present application;

Fig. 4 is a flow chart of another message conversion method provided by the present application;

Fig. 5 is a structural diagram of a message conversion system provided by the present application;

FIG. 6 is a structural diagram of another message conversion system provided by the present application;

FIG. 7 is a structural diagram of another message conversion system provided by the present application.

Detailed ways

The embodiments will be described in detail hereinafter, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following examples do not represent all implementations consistent with this application. These are merely examples of systems and methods consistent with aspects of the present application as recited in the claims.

Referring to FIG. 1, FIG. 1 is a flow chart of a message conversion method provided by the present application. As shown in Figure 1, the following steps are included:

Step 101. Receive a first message sent by a first device.

In step 101, the message conversion system may receive a first message sent by a first device. For example, the packet conversion system may receive the first packet sent by the underlying device.

Step 102: Analyze the first message to obtain the target identification address.

In step 102, the message conversion system may analyze the first message to obtain the target identification address.

Step 103: Select a target protocol analysis plug-in from at least two protocol analysis plug-ins according to the target identification address.

In step 103, the message conversion system may select the target protocol analysis plug-in from at least two protocol analysis plug-ins according to the target identification address. For example, the message conversion system can determine the target communication protocol according to the target identification address and the configuration file. Wherein, the configuration file includes the corresponding relationship between the identification address and the communication protocol. That is, the message conversion system can use the target identification address to match with the configuration file, and then determine the target communication protocol. Then, the message conversion system can select a target protocol analysis plug-in corresponding to the target communication protocol from at least two protocol analysis plug-ins according to the target communication protocol. That is, the message conversion system can select a target protocol analysis plug-in from at least two protocol analysis plug-ins according to the configuration file matching result.

Step 104: Use the target protocol parsing plug-in to convert the first packet to obtain a second packet.

In step 104, the message conversion system may use the target protocol analysis plug-in to convert the first message to obtain the second message. That is, the message conversion system can use the target specification parsing plug-in to convert the first message to obtain the second message in JavaScript object notation (Java Script Object Notation, JSON) format. That is, the message conversion system can convert the first message according to the parsing rules corresponding to the target protocol parsing plug-in, and encapsulate it into a second message in the common JSON format.

Step 105. Send the second message to the second device.

In step 105, the message conversion system may send the second message to the second device, that is, the message conversion system may send the second message in JSON format to the server.

It should be noted that different power communication protocol messages correspond to different parsing rules. In related technologies, since various power communication protocols are not compatible, different software systems need to be customized and developed for different smart devices, and message conversion is difficult.

However, in this application, different protocol analysis plug-ins are integrated into a packet conversion system in the form of plug-ins. This form makes it easy for the message conversion system to expand to support more Internet of Things protocols other than the power protocol. When the interface needs to be changed during the connection between the server side and the third-party system, there is no need to change any module in the protocol analysis plug-in. After the message conversion system receives the first message, it can select a target protocol analysis plug-in from at least two protocol analysis plug-ins, and use the target protocol analysis plug-in to convert the first message. There is no need to customize and develop different software systems for different smart devices, reducing the difficulty of message conversion, and the compatibility of the message conversion system is better.

The message conversion method provided by the present application receives the first message sent by the first device; parses the first message to obtain the target identification address; according to the target identification address, in at least two protocol analysis plug-ins Selecting a target protocol parsing plug-in; using the target protocol parsing plug-in to convert the first message to obtain a second message; sending the second message to the second device. In this way, after receiving the first message, the target protocol analysis plug-in can be selected from at least two protocol analysis plug-ins, and the first message can be converted by the target protocol analysis plug-in. There is no need to customize and develop different software systems for different smart devices, reducing the difficulty of message conversion, and the compatibility of the message conversion system is better.

Referring to FIG. 2, FIG. 2 is a flow chart of another message conversion method provided by the present application. As shown in Figure 2, it includes the following steps:

Step 201. Receive a first message sent by a first device.

In step 201, the message conversion system may receive a first message sent by a first device.

Step 202, analyze the first message to obtain the target identification address.

In step 202, the message conversion system may analyze the first message to obtain the target identification address.

Step 203. Determine the target communication protocol according to the target identification address and the configuration file, wherein the configuration file includes the correspondence between the identification address and the communication protocol.

In step 203, the message conversion system may determine the target communication protocol according to the target identification address and the configuration file. Wherein, the configuration file includes the corresponding relationship between the identification address and the communication protocol. That is, the message conversion system can use the target identification address to match with the configuration file, and then determine the target communication protocol.

Step 204: According to the target communication protocol, select a target protocol analysis plug-in corresponding to the target communication protocol from the at least two protocol analysis plug-ins.

In step 204, the message conversion system may select a target protocol analysis plug-in corresponding to the target communication protocol from at least two protocol analysis plug-ins according to the target communication protocol. That is, the message conversion system can select a target protocol analysis plug-in from at least two protocol analysis plug-ins according to the configuration file matching result.

Step 205: Use the target protocol parsing plug-in to convert the first packet to obtain a second packet.

In step 205, the message conversion system can use the target protocol analysis plug-in to convert the first message to obtain the second message.

Optionally, the receiving the first message sent by the first device includes:

receiving the first packet sent by the underlying device;

The step of using the target protocol parsing plug-in to convert the first message to obtain the second message includes:

Utilize the target specification analysis plug-in to convert the first message to obtain the second message in JavaScript Object Numbered Notation (JSON) format;

The sending the second message to the second device includes:

Send the second message in JSON format to the server.

For example, the packet conversion system may receive the first packet sent by the underlying device. It should be noted that different power communication protocol messages correspond to different parsing rules. The message conversion system can use the target specification parsing plug-in to convert the first message to obtain the second message in JSON format. That is, the message conversion system can convert the first message according to the parsing rules corresponding to the target protocol parsing plug-in, and encapsulate it into a second message in the common JSON format. Next, the message conversion system may send the second message in JSON format to the server.

Different protocol analysis plug-ins are integrated into a message conversion system in the form of plug-ins, and then the target communication protocol is determined according to the target identification address through the configuration file. Then call the relevant protocol parsing plug-in to parse different power communication protocol messages, and finally realize the conversion of different power communication protocol messages into general JSON messages.

The reason why the protocol analysis plug-in is used in the form of a plug-in is mainly to consider the expansion and compatibility of the message conversion system. This form makes the message conversion system easy to expand and support more IoT protocols except the power protocol. You only need to develop the required protocol analysis plug-ins in the form of plug-ins, and then they can be integrated into the message conversion system. When the interface needs to be changed during the connection between the server side and the third-party system, there is no need to change any module in the protocol analysis plug-in.

Optionally, the receiving the first message sent by the first device includes:

Receive the first message in JSON format sent by the server;

The step of using the target protocol parsing plug-in to convert the first message to obtain the second message includes:

Converting the first message in the JSON format by using the target protocol parsing plug-in to obtain a second message in the protocol message format;

The sending the second message to the second device includes:

Send the second packet in the protocol packet format to the underlying device.

The message conversion system may also receive the first message in JSON format sent by the server. Furthermore, the message conversion system can use the target protocol parsing plug-in to convert the received first message in JSON format to obtain the second message in the protocol message format. That is, the message conversion system can use the target protocol parsing plug-in to analyze the first message in the JSON format and encapsulate it into a second message in the protocol message format. Then, the message conversion system may send the second message in the protocol message format to the bottom layer device.

Compared with related technologies, the present application can reduce the difficulty of accessing the message conversion system for bottom-layer equipment, improve compatibility, and can also reduce the difficulty of real-time protocol conversion of communication protocols. Moreover, the development efficiency of the message conversion system is high, the development time is short, and the stability, reliability, scalability and compatibility of the message conversion system are better.

Optionally, the sending the second message in the protocol message format to the underlying device includes:

According to the target identification address, determine the underlying device with the target identification address;

Sending the second packet in the protocol packet format to the underlying device having the target identification address.

Further, the packet conversion system can determine the underlying device with the target identification address according to the target identification address. Furthermore, the message conversion system may send the second message in the specified message format to the underlying device having the target identification address.

Step 206: Send the second message to the second device.

In step 206, as mentioned above, the message conversion system may send the second message to the second device.

In the message conversion method provided by the present application, after receiving the first message, the first message can be analyzed to obtain the target identification address. Furthermore, the target communication protocol can be determined according to the target identification address and the configuration file. Then, according to the target communication protocol, select a target protocol analysis plug-in corresponding to the target communication protocol from at least two protocol analysis plug-ins, and use the target protocol analysis plug-in to convert the first message. Integrate different protocol analysis plug-ins into a packet conversion system in the form of plug-ins. This form makes it easy for the message conversion system to expand to support more Internet of Things protocols other than the power protocol. When the interface needs to be changed during the connection between the server side and the third-party system, there is no need to change any module in the protocol analysis plug-in. There is no need to customize and develop different software systems for different smart devices, reducing the difficulty of message conversion, and the compatibility of the message conversion system is better.

Referring to FIG. 3 , FIG. 3 is a flow chart of another message conversion method provided by the present application. As shown in Figure 3, the following steps are included:

Step 301, the underlying device uploads the message to the message conversion system.

Step 302, the data receiving module of the message conversion system receives the message uploaded by the underlying device.

Step 303, the data parsing module of the message conversion system parses the message uploaded by the bottom device to obtain the unique identification address of the bottom device.

Step 304, the configuration file parsing module of the message conversion system uses the unique identification address of the underlying device to match the configuration file, and then determines the target communication protocol.

Step 305, the message conversion system invokes the relevant protocol parsing plug-in according to the target communication protocol.

Step 306: The message conversion system converts the message uploaded by the underlying device according to the parsing rule corresponding to the relevant protocol parsing plug-in, and encapsulates it into a message in common JSON format.

It should be noted that different protocol parsing plug-ins can be integrated into a packet conversion system in the form of plug-ins. For example, as shown in FIG. 3 , the message conversion system may include 101 protocol analysis plug-ins, 104 protocol analysis plug-ins, serial communication protocol (Modbus) protocol analysis plug-ins, and so on. You can use the 101 protocol analysis plug-in to convert the 101 message uploaded by the underlying device and encapsulate it into a general JSON format message; you can use the 104 protocol analysis plug-in to convert the 104 message uploaded by the underlying device and encapsulate it into a general JSON format message Text; the Modbus protocol analysis plug-in can be used to convert the Modbus message uploaded by the underlying device and encapsulate it into a general JSON format message.

In step 307, the message conversion system can upload the message in common JSON format converted from the message uploaded by the underlying device to the server. It can realize the easy conversion of different power communication protocol messages into messages in common JSON format and access to the server.

The message conversion method provided by this application integrates different protocol analysis plug-ins into a message conversion system in the form of plug-ins. This form makes it easy for the message conversion system to expand to support more Internet of Things protocols other than the power protocol. When the interface needs to be changed during the connection between the server side and the third-party system, there is no need to change any module in the protocol analysis plug-in. There is no need to customize and develop different software systems for different smart devices, reducing the difficulty of message conversion, and the compatibility of the message conversion system is better.

Referring to FIG. 4, FIG. 4 is a flow chart of another message conversion method provided by the present application. As shown in Figure 4, the following steps are included:

Step 401, the server sends a message in common JSON format to the message conversion system.

Step 402, the data receiving module of the message conversion system receives the message in general JSON format delivered by the server.

Step 403, the data parsing module of the message conversion system parses the message in general JSON format sent by the server to obtain the unique identification address of the underlying device.

Step 404, the configuration file parsing module of the message conversion system uses the unique identification address of the underlying device to match with the configuration file, and then determines the target communication protocol.

Step 405, the message conversion system invokes the relevant protocol parsing plug-in according to the target communication protocol.

Step 406, the message conversion system uses the relevant protocol analysis plug-in to analyze the message in general JSON format issued by the server, and encapsulates it into a message in the protocol message format.

It should be noted that different protocol parsing plug-ins can be integrated into a packet conversion system in the form of plug-ins. For example, as shown in FIG. 4 , the message conversion system may include 101 protocol analysis plug-ins, 104 protocol analysis plug-ins, Modbus protocol analysis plug-ins, and the like. You can use the 101 protocol analysis plug-in to convert the general JSON format message sent by the server and encapsulate it into a 101 message; you can use the 104 protocol analysis plug-in to convert the general JSON format message sent by the server and encapsulate it into a 104 message Text; you can use the Modbus protocol analysis plug-in to convert the general JSON format message sent by the server and encapsulate it into a Modbus message.

In step 407, the message conversion system can deliver the message in the protocol message format converted from the message in the common JSON format delivered by the server to the underlying device. Further, the packet conversion system may determine the bottom device with the unique identification address according to the obtained unique identification address of the bottom device. Furthermore, the message conversion system can send a message in a standardized message format to the underlying device with the uniquely identified address. It is possible to easily convert messages in the common JSON format on the server side into messages of different power communication protocols and send them to the underlying devices.

The message conversion method provided by this application integrates different protocol analysis plug-ins into a message conversion system in the form of plug-ins. This form makes it easy for the message conversion system to expand to support more Internet of Things protocols other than the power protocol. When the interface needs to be changed during the connection between the server side and the third-party system, there is no need to change any module in the protocol analysis plug-in. There is no need to customize and develop different software systems for different smart devices, reducing the difficulty of message conversion, and the compatibility of the message conversion system is better.

Referring to FIG. 5, FIG. 5 is a structural diagram of a message conversion system provided by the present application. As shown in Figure 5, the message conversion system 500 includes a receiving module 501, an analysis module 502, a selection module 503, a conversion module 504 and a sending module 505, wherein:

a receiving module 501, configured to receive the first message sent by the first device;

A parsing module 502, configured to parse the first message to obtain a target identification address;

A selection module 503, configured to select a target protocol analysis plug-in from at least two protocol analysis plug-ins according to the target identification address;

A conversion module 504, configured to use the target protocol parsing plug-in to convert the first message to obtain a second message;

A sending module 505, configured to send the second message to the second device.

Optionally, as shown in FIG. 6, the selection module 503 includes:

The first determination sub-module 5031 is configured to determine the target communication protocol according to the target identification address and the configuration file, wherein the configuration file includes the correspondence between the identification address and the communication protocol;

The selection submodule 5032 is configured to select a target protocol parsing plug-in corresponding to the target communication protocol among the at least two protocol parsing plug-ins according to the target communication protocol.

Optionally, the receiving module 501 is configured to receive the first message sent by the underlying device;

The conversion module 504 is configured to convert the first message by using the target specification parsing plug-in to obtain a second message in JavaScript Object Numbered Notation (JSON) format;

The sending module 505 is configured to send the second message in JSON format to the server.

Optionally, the receiving module 501 is configured to receive the first message in JSON format sent by the server;

The conversion module 504 is configured to convert the first message in the JSON format by using the target protocol parsing plug-in to obtain a second message in the protocol message format;

The sending module 505 is configured to send the second message in the protocol message format to the underlying device.

Optionally, as shown in FIG. 7, the sending module 505 includes:

The second determining submodule 5051 is configured to determine the underlying device with the target identification address according to the target identification address;

The sending submodule 5052 is configured to send the second message in the protocol message format to the underlying device with the target identification address.

The message conversion system 500 can implement various processes implemented by the message conversion system in the method embodiments shown in FIGS. 1-4 . To avoid repetition, details are not repeated here. Moreover, the message conversion system 500 can analyze the first message after receiving the first message, and obtain the target identification address. Furthermore, the target communication protocol can be determined according to the target identification address and the configuration file. Then, according to the target communication protocol, select a target protocol analysis plug-in corresponding to the target communication protocol from at least two protocol analysis plug-ins, and use the target protocol analysis plug-in to convert the first message. Integrate different protocol analysis plug-ins into a packet conversion system in the form of plug-ins. This form makes it easy for the message conversion system to expand to support more Internet of Things protocols other than the power protocol. When the interface needs to be changed during the connection between the server side and the third-party system, there is no need to change any module in the protocol analysis plug-in. There is no need to customize and develop different software systems for different smart devices, reducing the difficulty of message conversion, and the compatibility of the message conversion system is better.

The similar parts between the embodiments provided in the present application can be referred to each other, and the specific implementations provided above are only a few examples under the general concept of the present application, and do not constitute a limitation of the protection scope of the present application. For those skilled in the art, any other implementations expanded based on the proposal of the present application without creative work shall fall within the scope of protection of the present application.

Claims (10)

1. a kind of message forwarding method characterized by comprising

Receive the first message that first device is sent；

First message is parsed, target identification address is obtained；

According to the target identification address, selection target specification parses plug-in unit at least two specifications parsing plug-in unit；

First message is converted using target specification parsing plug-in unit, obtains the second message；

Second message is sent to second device.

2. the method as described in claim 1, which is characterized in that it is described according to the target identification address, at least two rule It about parses selection target specification in plug-in unit and parses plug-in unit, comprising:

Destinations traffic specification is determined according to the target identification address and configuration file, wherein the configuration file includes mark Know the corresponding relationship of address and communication protocol；

According to the destinations traffic specification, selection and the destinations traffic specification pair at least two specification parsing plug-in unit The target specification parsing plug-in unit answered.

3. method according to claim 1 or 2, which is characterized in that first message for receiving first device and sending, packet It includes:

Receive first message that underlying device is sent；

It is described that first message is converted using target specification parsing plug-in unit, obtain the second message, comprising:

First message is converted using target specification parsing plug-in unit, obtains JavaScript object numbered musical notation (JSON) the second message of format；

It is described to send second message to second device, comprising:

The second message of the JSON format is sent to server.

4. method according to claim 1 or 2, which is characterized in that first message for receiving first device and sending, packet It includes:

Receive the first message of the JSON format that server is sent；

It is described that first message is converted using target specification parsing plug-in unit, obtain the second message, comprising:

The first message of the JSON format is converted using target specification parsing plug-in unit, obtains specification message format The second message；

It is described to send second message to second device, comprising:

The second message of the specification message format is sent to underlying device.

5. method as claimed in claim 4, which is characterized in that described to send the of the specification message format to underlying device Two messages, comprising:

According to the target identification address, determining has the underlying device of the target identification address；

The second message of the specification message format is sent to the underlying device with the target identification address.

6. a kind of message converting system characterized by comprising

Receiving module, for receiving the first message of first device transmission；

Parsing module obtains target identification address for parsing to first message；

Selecting module, for parsing selection target specification solution in plug-in unit at least two specifications according to the target identification address Analyse plug-in unit；

Conversion module obtains the second message for converting using target specification parsing plug-in unit to first message；

Sending module, for sending second message to second device.

7. message converting system as claimed in claim 6, which is characterized in that the selecting module includes:

First determines submodule, for determining destinations traffic specification according to the target identification address and configuration file, wherein The configuration file includes the corresponding relationship of mark address and communication protocol；

Submodule is selected, for parsing selection and institute in plug-in unit at least two specification according to the destinations traffic specification State the corresponding target specification parsing plug-in unit of destinations traffic specification.

8. message converting system as claimed in claims 6 or 7, which is characterized in that the receiving module is set for receiving bottom First message that preparation is sent；

The conversion module is used to convert first message using target specification parsing plug-in unit, obtains Second message of JavaScript object numbered musical notation (JSON) format；

The sending module is used to send the second message of the JSON format to server.

9. message converting system as claimed in claims 6 or 7, which is characterized in that the receiving module is for receiving server First message of the JSON format of transmission；

The conversion module is used to convert the first message of the JSON format using target specification parsing plug-in unit, Obtain the second message of specification message format；

The sending module is used to send the second message of the specification message format to underlying device.

10. message converting system as claimed in claim 9, which is characterized in that the sending module includes:

Second determines submodule, for determining that the bottom with the target identification address is set according to the target identification address It is standby；

Sending submodule, for sending the second of the specification message format to the underlying device with the target identification address Message.