WO2011091731A1

WO2011091731A1 - Data transmission device, data transmission method and data synchronization method

Info

Publication number: WO2011091731A1
Application number: PCT/CN2011/070380
Authority: WO
Inventors: 毛芊; 蔡振兴; 董庆军
Original assignee: 深圳市同洲电子股份有限公司
Priority date: 2010-02-01
Filing date: 2011-01-19
Publication date: 2011-08-04
Also published as: CN101854401A

Abstract

Provided are a data transmission device, data transmission method and data synchronization method, wherein the data transmission device includes a message conversion module, for constructing, according to received parameter information, a first message supported by a pre-configured transmission protocol, or for converting a received first message into a second message supported by a service logic, and a routing module, for routing the first message constructed by said message conversion module to a message outlet to send it to an opposite device, or for invoking said service logic to respond to the converted second message of said message conversion module. The present invention can simplify real-time receiving/sending of a message and synchronous receiving/sending of asynchronous data, and supports protocol plug in & out and multiple routing strategies, thereby reducing the development difficulty and system cost.

Description

Data transmission device, data transmission method and data synchronization method

This application claims priority to Chinese Patent Application No. 201019164030.5, entitled "Data Transmission Equipment, Method and Data Synchronization Method", filed on February 1, 2010, the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present invention relates to the field of computer technologies, and in particular, to a data transmission device, a data transmission method, and a data synchronization method. Background technique

A distributed system is a software system built on a computer network with a high degree of cohesion and transparency. With the widespread use of distributed systems, the interaction between systems becomes more and more complex, and the integration becomes more and more difficult.

In the existing distributed system, each system, such as a web (website) system, a service (service) system, and a hessian (lightweight remote tool) system, uses different protocols; when the system processes business logic, the protocol is first implemented. Adaptation, and then the business logic to achieve the conversion of the message itself, the usual message content is XML (Extensible Markup Language, Extensible Markup Language), the business logic needs to parse the content of the message before processing, and convert to POJO (Plain Ordinary Java Objects, simple Java objects) objects; then the system implements the routing function of the message by itself, and realizes the mutual routing of each system through the mesh structure.

The inventors found in the process of implementing the present invention that the existing system mainly has the following defects:

1. The protocol is not pluggable and difficult to develop. Since the protocol adaptation between the systems needs to be processed before the processing of the service logic, the service processing efficiency is low. At the same time, the protocol is not pluggable. When a new protocol needs to be used to interact with the external system, the system needs to perform the interface. Modification and development, it is difficult;

2. The message conversion is cumbersome. Due to different message formats, each message processing needs to implement multiple message format conversions, which is cumbersome to operate. In addition, the message format is highly dependent, and the format needs to be modified when the format changes, and the steps are cumbersome;

3. The system cost is high. The system implements the routing function of the message itself, which requires high coupling between the systems; because the routing is implemented through a complex mesh structure, when the routing policy changes, the phases Both the system and the interaction structure need to be modified, which is costly and is not conducive to data synchronization of the system. Summary of the invention

Aiming at the disadvantages of the prior art, the object of the present invention is to provide a data transmission device, a data transmission method, and a data synchronization method, which can simplify real-time sending and receiving of messages, and support protocol insertion and extraction and multiple routing strategies, thereby reducing development difficulty. Reduce system costs.

In order to achieve the above object, an embodiment of the present invention provides a data transmission device, including: a message conversion module, configured to construct a first message supported by a pre-configured transmission protocol according to the received parameter information, or to receive the first message The message is converted into a second message supported by the business logic;

And a routing module, configured to route the first message constructed by the message conversion module to the message exit to send to the peer device, or invoke the service logic to respond to the second message converted by the message conversion module.

Correspondingly, an embodiment of the present invention further provides a data transmission method, including:

And configuring, according to the received parameter information, a first message supported by the pre-configured transport protocol; and routing the first message to the message exit to send to the peer device according to the received parameter information and the pre-configured routing information.

Correspondingly, the embodiment of the present invention further provides another data transmission method, including:

Converting the received first message into a second message supported by the business logic;

The business logic is invoked in response to the second message based on pre-configured routing information.

Correspondingly, an embodiment of the present invention further provides a data synchronization method, including:

Constructing, according to the received parameter information, a first message supported by the pre-configured transport protocol; storing the content of the first message as synchronization data in a database, and loading all the synchronization data in the database;

The loaded synchronization data is sent to the peer device according to the pre-configured routing information to synchronize the data of the peer device.

The invention encapsulates and integrates functions such as protocol adaptation, message conversion, message routing and data synchronization to form a data transmission device, which can support plugging and unplugging various protocols and support various routing strategies; the data transmission device as a public The component can be used as the sender to process and send the message in real time, and can be used as the receiver to receive the message in real time; simplifying the conversion and realizing of the message Time to send and receive, reduce development and reduce development difficulty; In addition, without the need to modify the system and interaction structure or add corresponding functions, it can simplify the synchronous transmission and reception of asynchronous data, reducing system cost. DRAWINGS

1 is a schematic structural diagram of an embodiment of a data transmission device according to the present invention;

2 is a schematic structural diagram of an embodiment of a synchronization module according to the present invention;

3 is a flow chart of a first embodiment of a data transmission method of the present invention;

4 is a flow chart of a second embodiment of a data transmission method of the present invention;

FIG. 5 is a flow chart of an embodiment of a data synchronization method of the present invention. detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.

1 is a schematic structural diagram of an embodiment of a data transmission device according to the present invention. As shown in FIG. 1, the data transmission device includes: a message conversion module 20 and a routing module 30.

In a specific implementation, the data transmission device can be applied as a common component to the sender, the receiver, the client, and the server. For example, in a digital television receiving system, the data transmission device can be applied to a server, which is a sender of a message, and sends a corresponding message to the digital television receiving terminal through the transmission device, where the digital television receiving terminal includes It is not limited to: Set Top Box (STB), IPTV (Internet Protocol Television), TV mobile phone, digital TV integrated machine, etc., which have the function of receiving digital TV. For example, the data transmission device can also be applied to a digital television receiving terminal, which is a receiver of a message, receives a message sent by the front-end server through the transmission device, and invokes a corresponding service logic to respond to the message. It can be understood that the application of the data transmission device here is only an example, and similar analysis can be performed in other application situations, and details are not described herein. The first message supported by the conference, or converting the received first message into a second message supported by the business logic;

In a specific implementation, the parameter information includes a message body, a message entry address, and an operation code.

The routing module 30 is configured to route the first message constructed by the message conversion module 20 to a message exit to be sent to the peer device, or invoke the service logic to respond to the second message converted by the message conversion module 20. .

As further shown in FIG. 1, the data transmission device further includes: a pre-configuration module 10, an interaction module 40, and a synchronization module 50.

The pre-configuration module 10 is configured to pre-configure a transmission protocol and routing information. In a specific implementation, the pre-configuration module 10 is mainly used to implement insertion and removal of various protocols, and implement various routing policies. Generally, the message exchanged by the existing system is mainly an XML message, and the message format processed by the business logic is a message of the POJO object. Therefore, the pre-configuration module 10 pre-configures the transmission protocol, for example, pre-configuring the XML transmission protocol or The POJO transport protocol is such that the message conversion module 20 implements bidirectional conversion of XML and POJO objects according to a pre-configured protocol. It can be understood that the protocol type here is only an example, and other situations can be similarly analyzed, for example: When a new protocol needs to be used, the new protocol can be directly pre-configured, and the new protocol can be used in data transmission; For another example, when a certain protocol is not needed, the pre-configuration may not be performed before the data transmission, and details are not described herein. The pre-configuration module 10 implements plugging and unplugging and adaptation of protocols. In addition, according to actual needs, or system configuration, the pre-configuration module 10 pre-defines various routing policies to provide routing information for message transmission. Specifically, pre-configuration of various routing information and existing routing strategies are performed. The process of formulating routing information is similar and will not be described here.

The interaction module 40 is configured to provide an interface for externally interacting with a message, including a message interface that receives parameter information that is externally transmitted, a message entry that receives an external incoming first message, and a message exit that sends a message to the peer device. And the business interface that invokes the business logic to respond to the message.

In a specific implementation, the interaction module 40 provides an interface for various message interactions, which shields the processing of messages (including message conversion, message routing, protocol adaptation, etc.) within the data transmission device, and presents the information to the user only The processing of the business logic, that is, the user only needs to call the interface of the data transmission device to carry in the initial information, and then the data transmission device performs a series of processing and returns to the user. Specifically, when the user uses the data transmission device, the user first needs to invoke various interfaces of the interaction module 40 through an API (Application Programming Interface) to implement data transmission.

Specifically, when the data transmission device is applied to the message sending end, the user invokes the message interface of the interaction module 40 through an API call, as follows:

//UserRequestBody and UserResponseBody inherit the Body abstract class provided by the data transfer device.

Body requestBody = new UserRequestBody();

Body responseBody = new UserResponseBody();

IMessageSender sender = new MessageSender();

/ / Call the interface method to send a message, support extension when calling sendToSystem ()

ReturnMessage message = sender. sendToAAA(requestBody,

responseBody, "AAA- Query-User"); Through the above program, the sending message interface of the interaction module 40 can be invoked, and the user can pass the POJO object, the message entry address and the operation code of the message body part as parameters in the program. Into the data transmission device.

Specifically, the API calls when data synchronization is required are as follows:

Body requestBody = new UserRequestBody();

IMessageSync syncer = new MessageSync();

String resultID = syncer. syncMessage(requestBody, "AAA_ Query_User"," aaa. sync ") ; Through the above program, the synchronization interface of the interaction module 40 can be called, and the user can put the POJO object of the message body part, The message entry address and the opcode are passed as parameters to the data transmission device Medium.

It can be understood that the above API call is only an example, and other cases: For example: When the data transmission device is applied to the receiving end, or applied to the requested party of the synchronous data, the API call can be similarly analyzed. This will not be repeated.

The synchronization module 50 is configured to store the content of the first message constructed by the message conversion module 20 as synchronization data to a database, and load all synchronization data in the database; according to the pre-configured routing information, The routing module 30 sends the loaded synchronization data to the peer device to synchronize the data of the peer device.

In a specific implementation, the synchronization module 50 also returns a synchronization identifier to the calling party of the synchronization interface, and the synchronization interface caller considers that the data synchronization is completed after receiving the synchronization identifier, and the synchronous interface caller can also view according to the synchronization identifier. This data synchronization record includes viewing the synchronization data of this synchronization from the database, and the synchronization process to the peer device.

The invention encapsulates and integrates functions such as protocol adaptation, message conversion, message routing and data synchronization to form a data transmission device, which can support plugging and unplugging various protocols and support various routing strategies; the data transmission device as a public The component can be used as the sender to process and send the message in real time, and can be used as the receiver to receive and receive the message in real time. It simplifies the message conversion and real-time sending and receiving, reduces the development amount and reduces the development difficulty. The interaction structure can be modified or added with corresponding functions, which can simplify the synchronous sending and receiving of asynchronous data and reduce the system cost.

In order to explain the present invention more clearly, the synchronization module in the data transmission device will be described in detail below.

Referring to FIG. 2, it is a schematic structural diagram of an embodiment of a synchronization module according to the present invention. As shown in FIG. 2, the synchronization module 50 includes: a storage unit 501, a loading unit 502, and a synchronization unit 503.

The storage unit 501 is configured to store the content of the first message constructed by the message conversion module 20 as synchronization data to a database;

In a specific implementation, the transmission protocol pre-configured by the pre-configuration module 10 is an XML protocol. The message conversion module 20 first constructs a request header of an XML message according to the operation code, and according to the message body introduced in the interaction module 40. a parameter, converting a POJO object of the body into an XML object, and combining the request header into an XML request message; the storage unit 501 storing the content of the XML message as synchronization data in a database; The loading unit 502 is configured to load all synchronization data in the database;

In a specific implementation, the loading unit 502 is responsible for loading all the synchronization data in the database by loading the thread. Specifically, the loading unit may put the loaded synchronization data into the blocking data queue. Of course, synchronous data can also be placed in other data queues in memory, and the characteristics of the queue can be used to store synchronized data.

The synchronization unit 503 is configured to send, by using the routing module 30, the synchronization data loaded by the loading unit 502 to the peer device according to the pre-configured routing information, to synchronize data of the peer device.

In a specific implementation, the synchronization unit 503 reads data from the blocking queue by reading the thread, and sends data through the sending thread of the sending thread pool, and the sending thread is routed according to the message entry address parameter and the pre-configured routing information. The module 30 routes the message to the message exit and sends it to the peer device to synchronize the data of the peer device.

In the above process, the data transmission device is applied to the data synchronization client, and the synchronous data is sent in an asynchronous manner, which simplifies the synchronous transmission of the asynchronous data. It can be understood that when the data transmission device is applied to the data synchronization server, the data synchronization process can be similarly analyzed, and details are not described herein.

The invention can simplify the synchronous sending and receiving of asynchronous data without reducing the system and the interaction structure or adding corresponding functions, thereby reducing the system cost.

In order to explain the present invention more clearly, the data transmission method of the present invention will be described in detail below. 3 is a flowchart of a first embodiment of a data transmission method according to the present invention. The embodiment shown in FIG. 3 is an embodiment of a data transmission device applied to a sender for message transmission. As shown in FIG. The methods include:

S101, pre-configuring a transmission protocol and routing information;

In the specific implementation, the S101 is mainly used to implement insertion and removal of various protocols, and to implement various routing strategies. Generally, the messages exchanged by the existing system are mainly XML messages, and the message format processed by the business logic is a message of a POJO object. Therefore, the transmission protocol can be pre-configured, for example, a pre-configured XML transmission protocol or a POJO transmission protocol is implemented. Bidirectional conversion of XML and POJO objects. It can be understood that the protocol type here is only an example, and other situations can be similarly analyzed, for example: When a new protocol needs to be used, the new protocol can be directly pre-configured, that is, during data transmission. Use the new protocol; for example, when a certain protocol is not needed, it can be pre-configured before data transmission, and no comment is given here. S101 implements the insertion and removal and adaptation of the protocol. In addition, according to actual needs, or system configuration, various routing policies may be pre-defined to provide routing information for message transmission, specifically, pre-configuration of various routing information and existing routing information using various routing policies. Similarly, no comments are made here.

5102, receiving parameter information that is externally transmitted;

In the specific implementation, the external (for example, the user) may pass the message body, the message entry address, and the operation code as parameters through the method invoked by the API, and S102 receives the above-mentioned parameter information introduced by the user.

5103. Construct a first message supported by the pre-configured transport protocol according to the received parameter information. In the specific implementation, construct an XML message request header according to the opcode parameter, and then construct a XML according to the message body parameter and the message request header. Request message

S104: Route the first message to the message exit to send to the peer device according to the parameter information and the pre-configured routing information.

In a specific implementation, an API call may be performed according to the message entry address parameter, and the message is sent to the message portal, and the message portal selects a corresponding message exit according to the pre-configured routing information, and forwards the message to the message exit.

Referring to FIG. 4, it is a flowchart of a second embodiment of a data transmission method according to the present invention. The embodiment shown in FIG. 4 is an embodiment of a data transmission device applied to a receiving end for message reception and response; , the method includes:

S201. Receive an external first message by using a message portal.

In a specific implementation, the S201 receives, by using a message portal, a first message sent by the sending end, that is, an XML request message; 5202. Convert the received first message into a second message supported by the service logic. In a specific implementation, the S202 separately extracts the request header and the message body part in the XML request message, and converts the XML object of the message body part into a POJO object. Making it a second message supported by the business logic, and the second message includes a message body that is a POJO object;

S203: The service logic is invoked to respond to the second message according to the pre-configured routing information. In the specific implementation, according to the pre-configured routing information, the routing information herein is a service route that is determined according to each service logic. S203 responds to the second message by calling the corresponding service logic of the service interface according to the operation code included in the request header extracted in S202 and the pre-configured service route.

Referring to FIG. 5, it is a flowchart of an embodiment of a data synchronization method according to the present invention. The embodiment shown in FIG. 5 is an embodiment of a data transmission device applied to a data synchronization client. As shown in FIG. 5, the method includes:

S301, pre-configuring a transmission protocol and routing information;

In specific implementation, S301 is mainly used to implement plugging and unplugging of various protocols and to implement various routing strategies. Generally, the messages exchanged by the existing system are mainly XML messages, and the message format processed by the business logic is a message of a POJO object. Therefore, the transmission protocol can be pre-configured, for example, a pre-configured XML transmission protocol or a POJO transmission protocol is implemented. Bidirectional conversion of XML and POJO objects. It can be understood that the protocol type here is only an example, and other situations can be similarly analyzed, for example: When a new protocol needs to be used, the new protocol can be directly pre-configured, and the new protocol can be used in data transmission; For another example, when a certain protocol is not needed, the pre-configuration may not be performed before the data transmission, and no comment is made here. S301 implements the insertion and removal and adaptation of the protocol. In addition, according to actual needs, or system configuration, various routing policies may be pre-defined to provide routing information for message transmission, specifically, pre-configuration of various routing information and existing routing information using various routing policies. Similarly, no comments are made here. 5302, receiving externally passed parameter information;

In the specific implementation, the external (for example: the user) can invoke the synchronization interface of the data transmission device by using the method invoked by the API, and the message body, the message entry address, and the operation code are input as parameters, and S302 receives the above-mentioned parameter passed by the user. information.

5303. Construct a first message supported by the pre-configured transport protocol according to the received parameter. In the specific implementation, construct an XML message request header according to the opcode parameter, and then construct a XML according to the message body parameter and the message request header. Request message

5304. Store the content of the first message as synchronization data in a database.

5305, returning the synchronization identifier to the API interface caller;

In a specific implementation, since an external (for example, a user) invokes a synchronous interface of the data transmission device to implement data synchronization by using an API call method, when the external (eg, user) invokes the synchronization interface through the API, the corresponding parameter is input. The data transmission device returns the synchronization identifier to the outside (for example: the user), that is, the API interface caller, and the API interface caller receives the synchronization identifier, that is, the data synchronization is completed, and the API interface caller can also use the synchronization identifier. View this data synchronization record, including viewing the synchronization data of this synchronization from the database, as well as the synchronization process.

5306, loading all the synchronization data in the database;

In a specific implementation, all the synchronization data in the database is loaded by loading the thread, and specifically, the loaded synchronization data can be put into the blocking data queue. Of course, it is also possible to put the synchronous data into other data queues in the memory, and use the characteristics of the queue to store the synchronized data.

5307. Send synchronization data to the peer device according to the pre-configured routing information, to synchronize data of the peer device.

In a specific implementation, the S307 reads the data from the blocking queue by reading the thread, and then sends the data through the sending thread of the sending thread pool, and the sending thread sends the message by the routing module 30 according to the message entry address parameter and the pre-configured routing information. The routing message exit is sent to the peer device to synchronize the data of the peer device.

Specifically, when the data transmission device is applied to the synchronous data server for synchronous data reception and synchronization, the specific process may refer to the process of the data transmission device applied to the receiving end and the data synchronization client, and is not described herein.

Through the description of the above embodiments, the present invention through protocol adaptation, message conversion, message routing And data synchronization and other functions for package integration, forming a data transmission device, capable of supporting plugging and unplugging of various protocols and supporting various routing strategies; the data transmission device as a common component can be used as a sender for real-time processing of messages and Sending, and can be used as a receiver to receive and receive messages in real time; simplifying message conversion and real-time sending and receiving, reducing development and reducing development difficulty; In addition, it can be simplified without modifying the system and interaction structure or adding corresponding functions. Synchronous transmission and reception of asynchronous data reduces system cost.

The above is only a preferred embodiment of the present invention, and of course, the scope of the present invention is not limited thereto, and those skilled in the art can understand all or part of the process of implementing the above embodiments, and according to the present invention. The equivalent changes required are still within the scope of the invention.

Claims

Rights request

A data transmission device, comprising:

a message conversion module, configured to construct, according to the received parameter information, a first message supported by the pre-configured transport protocol, or convert the received first message into a second message supported by the service logic;

2. The device according to claim 1, further comprising:

Pre-configuration module for pre-configuring transport protocols and routing information.

3. The device according to claim 2, further comprising:

An interaction module, configured to provide an interface for message interaction to the outside of the data transmission device, where the interface includes a message interface that receives parameter information externally transmitted by the data transmission device, and receives an externally transmitted The message entry of a message, the message exit of the message sent to the peer device, and the service interface that invokes the service logic to respond to the message.

4. The device according to any one of claims 3, further comprising:

a synchronization module, configured to store the content of the first message constructed by the message conversion module as synchronization data to a database, load all synchronization data in the database; and load the data through the routing module according to the pre-configured routing information. The synchronization data is sent to the peer device to synchronize the data of the peer device.

The device of claim 4, wherein the synchronization module comprises: a storage unit, configured to store the content of the first message constructed by the message conversion module as synchronization data to a database;

a loading unit, configured to load all synchronization data in the database;

The synchronization unit is configured to send, by using the routing module, the synchronization data loaded by the loading unit to the peer device according to the pre-configured routing information, to synchronize data of the peer device.

6. A data transmission method, characterized in that:

The method according to claim 6, wherein the constructing the first message supported by the pre-configured transport protocol according to the received parameter information further includes:

The incoming parameter information is received, and the parameter information includes a message body, a message entry address, and an operation code.

The method according to claim 7, wherein the receiving the incoming parameter information further includes:

Pre-configure transport protocols and routing information.

9. A data transmission method, characterized in that:

The method according to claim 9, wherein the converting the received first message to the second message supported by the service logic comprises:

The incoming first message is received through the message portal.

11. A data synchronization method, characterized in that:

The method according to claim 11, wherein before the constructing the first message supported by the pre-configured transport protocol, the method further includes:

Pre-configure the transport protocol and routing information;

The incoming parameter information is received, and the parameter information includes a message body, an entry address, and an operation code.