TWI513237B - Off - site network information exchange and multiple communication protocol transmission system and its method - Google Patents

Description

Off-site network information exchange and multiple communication protocol transmission system and method thereof

The present invention relates to an off-site network information exchange and multiple communication protocol transmission system and method thereof, and more particularly to a message exchanged off-site network message constructed by using a custom-purpose XML message and message mediation platform (Message Oriented Middleware). A method of transmitting different communication protocols.

At present, the functions of the systems used in the system are still connected by one-to-one interface. The protocols used are different. Different functions have different interface specifications, and the connection modes between systems are also different. This method of connection requires a lot of manpower and time to develop the interface between the systems, and can not effectively manage the network connection between systems. N systems have N network connections, M functions have M function interface specifications, and the whole complexity is N*M. Once the system is more, the higher the complexity, the difficulty in providing subsequent service provision, as shown in the traditional interface mode shown in Figure 1. In this way, if you want to broadcast, make one-to-many transmission, and carry out cross-system information integration services, the difficulty is quite high.

In addition, the interface between the different systems is a specific message, and the interpretation and processing are difficult. The new system is added to the interface, and additional interface information needs to be understood.

It can be seen that there are still many shortcomings in the above-mentioned methods of use, which is not a good method, but needs to be improved.

In view of the shortcomings derived from the above-mentioned conventional methods, the inventors of the present invention have improved and innovated, and after years of painstaking research, they have successfully developed and completed this remote network information exchange and multiple communication protocol transmission system and its method. The above related disadvantages can be improved.

The object of the present invention is to provide an off-site network information exchange and multiple communication protocol transmission system and method thereof, which can solve complex information exchange between systems, and is used for transmitting network information and communication protocol communication; Can be customized and expanded. In this transmission system, it can be used for message exchange between systems. It can also use various XML to set parameters, restart services (such as Apache, FTP Server), and can also execute remote commands (such as : Set the remote system time), which simplifies the complexity of obtaining remote system information or controlling the remote system.

The second object of the present invention is to provide an off-site network information exchange and multiple communication protocol transmission system and method thereof, which can simplify the N system network connections into only one by using the Bus feature provided by the message mediation platform. The network is connected to the message mediation platform; and through the common XML message, the M functional interface specifications are simplified into a custom general XML message, and the transmission communication can be one-to-one and one-to-many (broadcast), simplifying The complexity of doing it in the past.

Another object of the present invention is to provide an off-site network information exchange and multiple communication protocol transmission system and method thereof, which can be easily expanded and interpreted by designing an XML Schema, and the interface system only needs to obtain an XSD file, that is, It can be processed to simplify the interpretation time and complexity of the previous system interface.

A further object of the present invention is to provide a remote network information exchange and multiple communication protocol transmission system and method thereof, which mainly utilizes two technologies of XML scalability and Bus characteristics of a message mediation platform, and uses a unique calculation algorithm. Law and process processing, design a transmission method for communication between systems.

The remote network information exchange and multiple communication protocol transmission system and method thereof for achieving the above object are developed by using a common XML exchange message between two remote network information systems (eg, service demand side and service provider). And using a message mediation platform (Message Oriented Middleware), service components, messaging components, and message receiving components to construct a transmission method that provides one-to-one, one-to-many messages by converting related services into Message, and then through the message mediation platform for the underlying XML message exchange, to achieve the key functions of this transmission method.

Please refer to FIG. 2 , which is a schematic diagram of an application architecture of the remote network information exchange and multiple communication protocol transmission system and method thereof. The figure shows that the two different network information systems are used by Message Oriented Middleware 2 . (for example, the service demand side and the service provider) through the development of a common XML exchange message for the transmission of multiple communication protocols.

Please refer to FIG. 3 , which is a system architecture diagram of the remote network information exchange and multiple communication protocol transmission system and method thereof according to the present invention. The remote network information system (eg, service demand terminal and service provider) is known from the figure. The message orientation platform (Message Oriented Middleware) 2 transmits and receives information through three components, such as the service component 201, the message transmission component 202, and the message receiving component 203. The service component 201 is mainly used for performing various service requirements. The message transmitting component 202 sets the service requirements processed by the service component 201, sets a one-to-one or broadcast message tag, and transmits the message by using the publishing function provided by the message mediation platform 2; the message receiving component 203 Use the subscription function provided by the message mediation platform 2 to receive the message and continue processing according to the destination, or discard the message.

Please refer to FIG. 4 , which is a schematic diagram of a functional module of the service component of the present invention, which is a system service state function module 301 , a read profile function module 302 , a system remote restart service function module 303 , and a remote execution SQL. The function module 304 and the remote system time function module 305 are composed of five functional modules, and each functional module is divided into a calling terminal and a called terminal, which are mainly judged by the XML message attribute value, and are the calling end. When the XML attribute is set to MesaageType=”request”, if the message is returned by the called end, the XML setting value is MessageType=”response”. Each function module has its function code as its execution judgment. The system service status function module 301 determines whether the service is normal by using the content information of the received XML message, and packages the result into an XML message, and transmits the result to the message mediation platform. In fact, the example can be as follows: When the caller sends a message in XML, its attribute value is <CommandOverMQ FunctionType=”1” MessageType=”request”>, where

(a).FunctionType=”1”, indicating the execution of the system service status function module;

(b).MessageType=”request”, indicating that this is a request message.

The following message:

<valuelist><key>MSSQL</key><value>1433</value></valuelist>, indicating whether the 埠1433 of MSSQL is required to be normal. The called terminal program connects to the 埠1433 through the Socket to judge. If it is normal, it will return 1, and if it is not normal, it will return 0. When the XML message is returned, the XML attribute will set MessageType=”response” because of the execution result.

The complete return message is as follows:

The read profile function module 302 mainly stores the setting information on the Global Server, so as to simplify the setting work during the maintenance, and use the content information of the received XML message to query the data in the database to set the content. Packaged into an XML message and passed back to the message mediation platform. The actual part can be exemplified as follows: When the caller sends a message in XML, its attribute value is <CommandOverMQ FunctionType=”2”MessageType=”request”>, where

(a).FunctionType=”2”, indicating that the function module for reading the profile is executed;

(b).MessageType=”request”, indicating that this is a request message.

When the request side receives a MessageType="request" message, the program will use <ID>TEST.C1.R.105.LAB</ID> to query the information stored in the database and the result key-value Return, such as system-Region=TL.

The reply message is as follows:

The system restarts the service function module 303 in an off-site manner, and restarts the service of the remote system. It uses the content information of the received XML message to restart the specified service through the instruction, and the result is packaged into an XML message and transmitted back to the message mediation platform. In fact, the examples can be as follows:

When the caller sends a message in XML, its attribute value is <CommandOverMQ FunctionType=”3”MessageType=”request”>, where

(a).FunctionType=”3”, indicating the execution of the system service status function module;

(b).MessageType=”request”, indicating that this is a request message.

The following message:

<ValueList><Key>restartWinApache</Key><Value>net stop apache;netstart apache</Value></ValueList>, indicating that Apache Server needs to be restarted. The called end will execute the net stop apache and net start apache to restart the Apache service through the program, and return the result. If it is normal, it will return 1 and if it is not normal, it will return 0. When the XML message is returned, the XML attribute will set MessageType=”response” because of the execution result.

The reply message is as follows:

<CommandOverMQ FunctionType=”3”MessageType=”response”><valuelist><key>restartWinApache</key><value>1</value></valuelist>.

The remote execution SQL command function module 304 can send the SQL command to be executed to the remote server for execution, and return the result. It uses the content information of the received XML message, executes the SQL command through the database, and packages the result into an XML message, which is transmitted back to the message mediation platform. In fact, the examples can be as follows:

When the caller sends a message in XML, its attribute value is <CommandOverMQ FunctionType=”4”MessageType=”request”>.

among them

(a).FunctionType=”4”, indicating that the remote execution of the SQL command function module is executed;

(b).MessageType=”request” indicates that this is a request message.

The following message:

<ValueList><Key>sqlScript</Key><Value>select f1,f2,f3 from tableName</Value></ValueList><ValueList><Key>sqlExecuteQueryID</Key><Value>12345612</Value>< /ValueList>, which means that the SQL database query command of "select f1, f2, f3 from tableName" is sent to the remote database query. sqlExecuteQueryID=12345612 indicates the identification code of this query for identification. The called end will connect to the database through the program, execute select f1, f2, f3 from table query syntax, and return the query result. When the XML message is returned, the XML attribute will set MessageType=”response” because of the execution result.

The reply message is as follows:

The remote system time function module 305 is set to use this function to perform system time adjustment in a unified manner in some application fields. It uses the content information of the received XML message, performs date and time setting work through system instructions, and packages the result into an XML message and transmits it back to the message mediation platform. In fact, the examples can be as follows:

When the caller sends a message in XML, its attribute value is <CommandOverMQ FunctionType=”5”MessageType=”request”>, where

(a).FunctionType=”5”, indicating the execution of the system service status function module;

(b).MessageType=”request”, indicating that this is a request message.

And the following message:

, indicating that the time 2008/10/17 08:30:32 is sent to the remote system for setting. When the called party receives the request message, it will execute the time setting through the program and return the result. If it is normal, it will return 1 and if it is not, it will return 0. When the XML message is returned, the XML attribute will set MessageType=”response” because of the execution result.

The reply message is as follows:

Referring to FIG. 5, a schematic diagram of a message transmission/reception process of a message transmitting/receiving component of a message transmitting/receiving component according to the present invention, wherein the message transmitting component 202 performs a message transmission operation, and the steps thereof include:

(A) Set the target source and destination of the message processed by the service element 201, and decide whether to broadcast, if it is a single message transmission, set the destination area ID, and if it is for broadcast transmission, set the destination area ID=*;

(B) converting the object into an XML message 402 through the program;

(C) The delivery program then transmits the message to the message mediation platform 403 via the publishing method provided by the message mediation platform. The message receiving component 203 performs a message receiving operation, and the steps thereof include:

(a) receiving the message via the Message Intermediary Platform (MoM) subscription feature 404;

(b) converting the XML message into object 405 through the program;

(c) Next, determine whether its Target destination ID parameter is * (broadcast) or its own identification code 406 (one to one)

(d) If it is its own identification code, the message is forwarded to the service element 201 for processing. If not, ignore this message. By determining the Target ID, it is possible to achieve the functions of broadcasting, one-to-one transmission and the like.

Please refer to FIG. 6 , which is a definition specification of the general-purpose customized XML of the present invention, so as to standardize the underlying transmission message. The parameters defined by it include:

1. FunctionType 501, used to determine the type of service module, for example: FunctionType=1, indicating that the system service status query 301 is to be used; FunctionType=2, indicating that the read profile function 302 is to be used; FunctionType=3, indicating that it is Use the system to restart the service 303; FunctionType=4, indicating that the SQL command function 304 is to be executed remotely; FunctionType=5, indicating that the set system time service 305 is to be used;

2. MessageType 502, the decision message is a request or a result, currently defined by request, response, etc.;

3. Target 503, divided into To 505 and From 506, each with an ID 509 and IP 510 information. If you want to broadcast, ID 509 only needs to fill in "*". If it is one-to-one, you only need to fill in the specific system ID 509, and ID 509 needs to be unique;

4. ValueList 504, divided into Key 507 and Value 508, fill in the message to be delivered, and store it in the form of Key-value, which can be used for different applications, including request message and reply message.

According to the above XML definition, the present invention customizes five kinds of transmission XML messages, namely, system service state XML message, read profile XML message, system remotely restart service XML message, remote execution SQL instruction XML message, and set remote end. The system time XML, etc., are actually as follows:

(1) System Service Status XML Message Example: Set FunctionType="1" to indicate the use of system service status, and then set the caller and called information <Target><To><ID>TEST.C1.R.105. LAB</ID></To><From><ID>global</ID></From>, then set the <ValueList> attribute, fill in the name of the system service you need to fill in Key and Port. In the value, the service name and port can be expanded arbitrarily. The embodiment information is as follows:

When returning the result, set the <ValueList/> attribute, fill in the name of the system service, the service status is normal with 1, 0 means abnormal, fill in the value, set as follows:

The complete message is as follows:

a. Caller message:

b. Return message:

(2) Read the configuration file XML message embodiment:

Set FunctionType="2" to use the read profile information, then set the caller and called information <Target><To><ID>global</ID></To><From><ID>TEST. C1.R.105.LAB</ID></From></Target>, the caller does not need to set the <ValueList/> attribute, the function module will find <ID>TEST.C1.R.105 from the database. .LAB</ID> All relevant setting information is returned. For the return, the <ValueList/> attribute needs to be set. Here, the Key of the configuration file needs to be filled in the Key and the Value of the configuration file is filled in the value, and the number can be expanded arbitrarily. , its settings are as follows:

The complete message is as follows:

a. Caller message:

b. Return message:

(3) The system restarts the service XML message in different places:

Set FunctionType="3" to use the system to restart the service offsite, and then set the caller and called information <Target><To><ID>TEST.C1.R.105.LAB</ID></To> <From><ID>global</ID></From>, then set the ValueList> attribute, fill in the name of the instruction and the content of the execution instruction into the value, and the name and content of the instruction can be expanded arbitrarily. Its settings are as follows: <ValueList><Key>restartWinApache</Key><Value>net stop apache t;net start apache</Value></ValueList><ValueList><Key>restartLinApache</Key><Value>/etc /init.d/httpd restart</Value></ValueList>, when returning the result, set the <ValueList/> attribute, fill in the instruction name with key, the execution result is normal with 1, 0 means abnormal, fill in Value , set as follows: <ValueList><Key>restartWinApache</Key><Value>1</Value></ValueLiSt><ValueList><Key>restartLinApac he</Key><Value>0</Value></ValueList >

The complete message is as follows:

a. Caller message:

b. Return message:

(4) Remote execution of the SQL instruction XML message. Example: Setting FunctionType="4" means using the remote execution SQL command, first setting the caller and the called party information <Target><To><ID>TEST.C1. R.105.LAB</ID></To><From><ID>global</ID></From>, then the ValueList> property, which is set as follows: <ValueList><Key>sqlScript</Key><Value>select f1,f2,f3 from tableName</Value></ValueList><ValueList><Key>sqlExecuteQueryID</Key><Value>12345612</Value></ValueList>, indicating select f1,f2, F3 from tableName The SQL command is sent to the remote database for query. sqlExecuteQueryID=12345612 indicates the identification code of this query for identification. When executed by the calling end, select f1, f2, f3 from tableName query syntax, and return the query result, such as: <ValueList><Key>SqlExecuteQueryID</Key><Value>12345612</Value></ValueList><ValueList><Key>rowAmount</Key><Value>12</Value></ValueList><ValueList><Key>colName</Key><Value>f1 ^{^} f2 ^{^} f3</Value></ValueList><ValueList><Key>rowNum:1</Key><Value>r1 ^{^} r2 ^{^} r3</Value></ValueList><ValueList><Key>rowNum:2</Key><Value>r1 ^{^} r2 ^{^} r3</Value></ValueList>. SqlExecuteQueryID represents the query identification code, for identification, rowAmount represents the number of data, colName represents the field name, separated by ^{^} , convenient for parsing, rowNum: 1 indicates the first data, r1 ^{^} r2 ^{^} r3 indicates the first pen The field value in the data is separated by ^{^} , which is convenient for analysis.

The complete message is as follows:

a. Caller message:

b. Return message:

(5) Setting the remote system time XML embodiment:

Setting FunctionType="5" means using the set remote system time function, first setting the information of the calling end and the called end:

<Target><To><ID>TEST.C1.R.105.LAB</ID></To><From><ID>global</ID></From>, then set the <ValueList> attribute. Here you need to fill in the parameter values that need to be corrected. Example: <ValueList><Key>date</Key><Value>2008/10/17</Value></ValueList><ValueList><Key>time</ Key><Value>08:30:32</Value></ValueList> means that the date and time 2008/10/17 08:30:32 are sent to the remote system for setting. When returning the result, set the <ValueList/> attribute, fill in the name of the instruction, the execution result is normal with 1, 0 means abnormal, fill in Value, set as follows:

<va1uelist><key>returnCode</key><value>1</value></valuelist>.

The complete message is as follows:

a. Caller message:

b. Return message:

Referring to Figure 7, a flow chart of the present invention will be described in one embodiment. If you want to know whether all the MSSQL database services of the system are normal, you can use the broadcast method to post the message to the message mediation platform. If there is a message intermediary platform, the service result will be answered. Referring to FIG. 7, first, the FunctionType 601 is set first, and its value is set to 1, and the table is to execute the system service status query function 301. Next, set MessageType 602, and its value is set to request, indicating that this is a service request message. The request parameter 603 is set again, because the MSSQL service state is known, so the value is set to <valuelist><key>MSSQL</key><value>1433</value></valuelist>. Then set Target 604, because all the servers to be taken have their MSSQL service status, so its ID is set to *, and its full setting is <Target><To><ID>*</ID></To><From ><ID>globalServer</ID></From></Target>, which means that you want to get all the service status from the globalServer. At this point the complete XML message 605 is as follows: <CommandOverMQ FunctionType="1" MessageType="request"><Target><To><ID>*</ID></To><From><ID>globalServer</ID> <Rrom></Target><ValueList><Key>MSSQL</Key><Value>1433</Value></ValueList></Comm andOver>. At this time, the XML message 604 is posted through the message brokering platform (MoM) 606.

On other servers, the subscription message brokering platform (MoM) 607 will receive the request message 604 and determine if <Target><To><ID>*</ID></To> is * (table broadcast) ), or its own identification number. If not, it will ignore the no processing. If it is, then judge whether the MessageType is "request". If not, it will ignore the no processing. If yes, then the FunctionType attribute value is obtained. This embodiment is equal to 1, indicating that the system service status query function 301 is to be called. At this time, the program reads <ValueList><Key>MSSQL</Key><Value>1433</Value></ValueList>, and learns that it is 1433, and then uses Socket to connect to 埠1433. If it is a normal connection, fill in the result. 1, the connection is not on or there is an exception, the table is not normal, fill the result with 0 and then set the result parameter 612 as follows: <ValueList><Key>MSSQL</Key><Value>1</Value></ValueList> . Then set MessageType 613, because it is a postback message, it is set to "response". The FunctionType 614 is set to have a value of 1, which is a system service status query function 301. Then set <Target><To><ID>globalServer</ID></To><From><ID>Server1</ID></From></Target>, which will be on the server (Server1). The MSSQL service status is passed back to the globalServer. At this point the full XML message is <CommandOverMQ FunctionType="0" MessageType="response"><Target><To><ID>globalServer</ID></To><From><ID>Server1</ID></ From></Target><ValueLiSt><Key>MSSQL</Key><Value>1</Value></ValueList></CommandOver> then posts the message through the messaging platform.

At this time, after the server (globalServer) subscribes to the message from the message mediation platform and receives the message, it first determines whether <Target><To><ID>globalServer</ID></To> is equal to its own identification number. If not, it will ignore the no processing. If yes, then judge whether the MessageType is "response". If not, it will ignore the no processing, if it is the return result. At this point, as long as all the reply messages are collected, the service status of the relevant server can be known. According to this embodiment, <Target><To><ID>globalServer</ID></To><From><ID>Server1< /ID></From></Target><ValueList><Key>MSSQL</Key><Value>1</Value></ValueList></Comman dOver>, indicating the MSSQL service on the server (server1) The status is normal (value is 1).

The remote network information exchange and multiple communication protocol transmission system and method provided by the invention have the following advantages when compared with other conventional methods:

1. The present invention simplifies the complexity of inter-system connection through a single transmission method: each system only needs one connection to the message intermediation platform, and can exchange various messages and call different functional services, improving the previous N system interfaces. The disadvantage of N connections.

2. The present invention utilizes a single transmission method to achieve the purpose of remote network communication: the transmission method of the present invention uses a common XML definition to enable different functions to use the same transmission specification. Improve the shortcomings of the previous M functions with one M transmission specification.

3. The present invention utilizes a single transmission method to perform broadcast/one-to-one message exchange: through the message mediation platform, one-to-one and broadcast transmission modes can be performed, which increases the efficiency and improves the complexity of the previous implementation.

The detailed description of the preferred embodiments of the present invention is intended to be limited to the scope of the invention, and is not intended to limit the scope of the invention. The patent scope of this case.

To sum up, this case is not only innovative in terms of technical thinking, but also able to enhance the above-mentioned multiple functions compared with conventional articles. It should be submitted in accordance with the law in accordance with the statutory invention patents that fully meet the novelty and progressiveness, and you are requested to approve this article. Invention patent application, in order to invent invention, to the sense of virtue.

1. . . Interface access data system

2. . . Message Oriented Middleware

3. . . Custom XML message format

201. . . Service component

202. . . Message transmission component

203. . . Message receiving component

301. . . System service status function module

302. . . Read profile function module

303. . . System restarts service function module

304. . . Remote execution of SQL command function module

305. . . Set the remote system time function module

401. . . Set the Target source and destination and decide whether to broadcast

402. . . Convert a program object into a generic XML message

403. . . Publish generic XML messages to MoM via Message Intermediary Platform (MoM)

404. . . Subscribe to messages on MoM via Message Intermediary Platform (MoM)

405. . . Convert XML messages into program objects

406. . . Determine whether the Target destination is equal to its own ID or * (table broadcast)

501. . . FunctionType (determines the call function module attribute value)

502. . . MessageType (determines whether the message is a request or a result)

503. . . Target (represents source and destination)

504. . . ValueList (represents the message value of the request or result)

505. . . To (indicating the destination setting)

506. . . From (indicating source setting)

507. . . Key (identification key for customization)

508. . . Value (the value of the identification key for customization)

509. . . ID (representing the identification of the source or destination)

510. . . IP (represents the source or destination server address)

601. . . Set FunctionType

602. . . Set MessageType=”request”

603. . . Set request parameters (ValueList)

604. . . Set Target to determine source and destination

605. . . Request side XML message

606. . . Send messages via the message mediation platform (MoM)

607. . . Receive messages via the Message Intermediary Platform (MoM) subscription

608. . . Filter the Targer ID, only the destination is the broadcast and its own message

609. . . Determine if MessageType is equal to "request"

610. . . Call the corresponding function module according to functionType

611. . . The function module processes the request message and returns the result

612. . . Fill in the result of the function module into <valueList/>

613. . . Set MessageType=”response”

614. . . Set FunctionType

615. . . Set Target to determine source and purpose

616. . . The called end returns the XML message

617. . . Send messages via the message mediation platform (MoM)

618. . . Receive messages via the Message Intermediary Platform (MoM) subscription

619. . . Filter the Targer ID and only charge the message whose destination is itself

620. . . Determine if MessageType is equal to "response"

621. . . Presenting execution results

Figure 1 is a schematic diagram of a conventional interface;

2 is a schematic diagram of an application architecture of an alien network information exchange and multiple communication protocol transmission system and method thereof according to the present invention;

Figure 3 is a system architecture diagram of the remote network information exchange and multiple communication protocol transmission system and method thereof;

FIG. 4 is a schematic diagram of functional modules of the service elements of the remote network information exchange and multiple communication protocol transmission system and method thereof;

FIG. 5 is a schematic diagram of a message transmission/reception process of the message transmitting/receiving component of the remote network information exchange and multiple communication protocol transmission system and method thereof;

Figure 6 is a schematic diagram of a generalized custom XML definition of the remote network information exchange and multiple communication protocol transmission system and method thereof;

Figure 7 is a complete flow chart of the remote network information exchange and multiple communication protocol transmission system and method thereof.

1. . . Interface access data system

2. . . Message Oriented Middleware

3. . . Custom XML message format

Claims (11)

An off-site network information exchange and multiple communication protocol transmission system includes: a message mediation platform, which provides a service request end and a service provider end to transmit information in a general-purpose customized XML definition specification; a service component, processing The service demand side and the service provider's various service requirements; a messaging component that sets the one-to-one or broadcast message tag to the service component processing service request, and uses the publishing function provided by the message mediation platform to send the message Transmitted; a message receiving component that uses the subscription function provided by the message brokering platform to receive the message and continue processing according to the destination, or discard the message. For example, the remote network information exchange and multiple communication protocol transmission system described in claim 1 wherein the parameter defined by the definition specification of ‧ XML may include: (A) FunctionType, indicating the attribute of the call service component function module (B) MessageType, indicating the type of the message is the request or the result; (C) Target, indicating the source and destination; (D) ValueList, indicating the message value of the request or result. For example, the remote network information exchange and multiple communication protocol transmission system described in claim 2, wherein the source and destination parameters may include the identification value of the source or destination and the server address of the source or destination. . For example, the remote network information exchange and multiple communication protocol transmission system described in claim 2, wherein the message value of the request or result is stored in a key-value manner, wherein Key represents an identification key, and value represents an identification key. The value. For example, the remote network information exchange and multiple communication protocol transmission system described in claim 1 wherein the service component comprises: a system service status function module, which can use the content information of the received XML message to determine whether the service is Normal, and the result is packaged into an XML message, which is sent back to the message mediation platform. A read profile function module can use the content information of the received XML message to query the database to set the content and package the result into an XML message. , back to the message mediation platform; a system to restart the service function module, can use the content information of the received XML message, restart the specified service through the instruction, and package the result into an XML message, back Passed to the message mediation platform; a remote execution SQL command function module can use the content information of the received XML message, execute the SQL command through the database, and package the result into an XML message, and then transmit it to the message mediation platform; The remote system time function module can use the content information of the received XML message to perform date and time setting work through system instructions, and The result is wrapped into an XML message and passed back to the message mediation platform. The remote network information exchange and multiple communication protocol transmission system described in claim 5, wherein the XML message received by the system service status function module is a system service status XML message to obtain a key-value thereof. Information about the services defined by the form. The remote network information exchange and multiple communication protocol transmission system described in claim 5, wherein the XML message received by the read profile function module is a read profile XML message to read the key The XML message passed by the underlying information defined by the -value form. For example, the remote network information exchange and multiple communication protocol transmission system described in claim 5, wherein the system restarts the XML message received by the service function module to restart the service XML message for the system to obtain the The system defined by the form of key-value restarts the XML message passed by the underlying service function. For example, the remote network information exchange and multiple communication protocol transmission system described in claim 5, wherein the remote execution SQL command function module receives the XML message to remotely execute the SQL instruction XML message to obtain the key. The -value form defines the XML message passed by the underlying execution of the SQL instruction function. For example, the remote network information exchange and the multiple communication protocol transmission system described in claim 5, wherein the remote system time function module receives the XML message to set the remote system time XML message to obtain the key. The -value form defines the XML message passed by the underlying system time function. A remote network information exchange and multiple communication protocol transmission method, the steps comprising: (A) the service component of the service requesting end sets its function module parameters according to the service request, including: FunctionType, MessageType and ValueList; (B) service requesting end The message transmitting component sets the message processed by the service component, sets the target source and destination, and determines whether to broadcast; (C) the message transmitting component of the service requesting end converts the object of step (B) into an XML message through the program, and Transmitting the message to the message mediation platform through the publishing method provided by the message mediation platform; (D) the message receiving component of the service provider receives the message through the message mediation platform, and then converts the XML message into an object; (E) The message receiving component of the service provider then determines whether the Target destination ID parameter of the step (D) object is a broadcast or a one-to-one identification code. If it is a one-to-one identification code, the message is forwarded to the service component. Processing, otherwise ignore this message; (F) the service provider's service component executes the corresponding function module according to the FunctionType and MessageType parameters To process the request instruction and return the processing result; (G) the service component of the service provider sets the parameters such as FunctionType, MessageType, and ValueList of the backhaul result; (H) the message that the message delivery component of the service provider processes the service component, Set the Target source and destination, then convert the object into an XML message, and send the message to the message mediation platform through the publishing method provided by the message mediation platform; (I) the message receiving component of the service requesting terminal subscribes through the message mediation platform Function, receive the message, then convert the XML message into an object, and then determine whether the Target destination ID parameter of the object is a broadcast or a one-to-one identification code. If it is a one-to-one identification code, then the message is forwarded to the service. The component is processed, otherwise the message is ignored; (J) the service component of the service requester determines whether it needs to be processed according to the MessageType, and if it needs to be processed, the execution result is presented.