CN116506501A - Message forwarding method, device, electronic device and storage medium - Google Patents

Abstract

The application provides a message forwarding method, a message forwarding device, electronic equipment and a storage medium, and can be used in the technical field of distributed middleware. The method comprises the following steps: determining message forwarding information corresponding to the first message middleware and the second message middleware, wherein the types of the first message middleware and the second message middleware are different, and the message forwarding information is used for indicating respective transmission configurations of the first message middleware and the second message middleware; based on the message forwarding information, establishing long connection with the first message middleware and the second message middleware respectively; receiving a first message sent by a first message middleware according to the long connection with the first message middleware; converting the first message into a second message according to the message format of the second message middleware; and sending the second message to the second message middleware according to the long connection with the second message middleware. According to the method, the transmission of the message in different message middleware is realized through message conversion, and the stability and reliability of message transmission are improved.

Description

Message forwarding method, device, electronic device and storage medium

technical field

The present application relates to the technical field of distributed middleware, and in particular to a message forwarding method, device, electronic equipment and storage medium.

Background technique

Message middleware (MQ, Message Queue) is a message queue used to establish channels between systems for network communication and send data or files. The message provider can send the message to the message middleware. The message consumer can obtain the required message from the message middleware and process the obtained message. The more common message middleware may include different types of message middleware such as IBMMQ (International Business Machines Corporation MQ, International Business Machines Message Middleware), TDMQ (Tencent Distributed Message Queue, Tencent Cloud Middleware).

In practical applications, message communication cannot be performed between different types of message middleware. For example, IBMMQ messages provided by nodes using IBMMQ cannot be transmitted to nodes using TDMQ, and TDMQ messages provided by nodes using TDMQ cannot be transmitted to nodes using IBMMQ. node. Therefore, how to enable messages defined by different types of message middleware to communicate with each other is a technical problem to be solved urgently.

Contents of the invention

The present application provides a message forwarding method, device, electronic equipment and storage medium to solve the technical problem that messages defined by different types of message middleware cannot communicate with each other.

In a first aspect, the present application provides a message forwarding method, including:

Determine message forwarding information corresponding to the first message middleware and the second message middleware, the first message middleware and the second message middleware are of different types, and the message forwarding information is used to indicate that the first message middleware The respective transmission configurations of the middleware and the second message middleware;

Establishing a long connection with the first message middleware and the second message middleware respectively based on the message forwarding information;

Receive the first message sent by the first message middleware according to the long connection with the first message middleware;

converting the first message into a second message according to the message format of the second message middleware;

Send the second message to the second message middleware according to the long connection with the second message middleware.

In a second aspect, the present application provides a message forwarding device, including:

A determining unit, configured to determine message forwarding information corresponding to the first message middleware and the second message middleware, where the types of the first message middleware and the second message middleware are different, and the message forwarding information is used to indicate the Respective configuration parameters of the first message middleware and the second message middleware;

An establishing unit, configured to respectively establish a long connection with the first message middleware and the second message middleware based on the message forwarding information;

a receiving unit, configured to receive the first message sent by the first message middleware according to the long connection with the first message middleware;

A conversion unit, configured to convert the first message into a second message according to the message format of the second message middleware;

A sending unit, configured to send the second message to the second message middleware according to the long connection with the second message middleware.

In a third aspect, the present application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

the memory stores computer-executable instructions;

The processor executes the computer-executed instructions stored in the memory, so as to implement the method described in the first aspect and various possibilities of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to implement the first aspect and the first aspect when executed by a processor various possible methods.

In a fifth aspect, the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, the steps of the first aspect and various methods that may be involved in the first aspect are implemented.

The technical solution provided by this application can determine the message forwarding information of the first message middleware and the second message middleware. The message forwarding information is used to indicate the respective configuration parameters of the two message middleware. Through the message forwarding information, it is possible to establish The long connection with the first message middleware and the second message middleware realizes the use of electronic equipment as the transmission medium, respectively establishes long connections with the two message middleware, and then realizes the simultaneous transmission between the two message middleware. The establishment of the road. Through this long connection, it is possible to receive and configure the first message sent by the first message middleware, and convert the first message into a second message according to the message format of the second message middleware, so that the second message is adapted to The second message middleware is used to send the second message to the second message middleware according to the long connection, so as to realize message transmission between different message middlewares and improve the stability of message transmission between different message middlewares.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application.

FIG. 1 is a system architecture diagram for implementing a message forwarding method provided by an embodiment of the present application;

FIG. 2 is a flowchart of an embodiment of a message forwarding method provided in an embodiment of the present application;

FIG. 3 is a flow chart of another embodiment of a message forwarding method provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of an embodiment of a message forwarding device provided in an embodiment of the present application;

FIG. 5 is a block diagram of an electronic device for implementing a message forwarding method provided by an embodiment of the present application.

By means of the above drawings, specific embodiments of the present application have been shown, which will be described in more detail hereinafter. These drawings and text descriptions are not intended to limit the scope of the concept of the application in any way, but to illustrate the concept of the application for those skilled in the art by referring to specific embodiments.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, 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 exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present application as recited in the appended claims.

It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all It is information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation portals for users to choose to authorize or refuse.

It should be noted that the message forwarding method, device, electronic device, and storage medium provided by this application can be used in the technical field of distributed middleware, and can also be used in any field other than the technical field of distributed middleware. The application fields of the message forwarding method, device, electronic equipment and storage medium are not limited.

In related technologies, message middleware can be used as a medium between a message provider and a message consumer. The message provider can store messages in the message middleware, and the message consumer can pull messages from the message middleware and perform corresponding message processing. At present, the more common message middleware can include IBMMQ, TDMQ, etc. The message transmission formats of different message middleware are different, so the messages between different message middleware cannot be transmitted to each other. For example, messages stored in IBMMQ cannot be sent to TDMQ, and messages stored in TDMQ cannot be sent to IBMMQ.

In order to solve the above technical solution, taking into account the difference in the message structure of the message middleware, the messages of the two different message middleware can be re-encapsulated using the message conversion method, so that the re-encapsulated message is suitable for another message middleware cluster . The repackaged messages need to be transmitted between the clusters configured with two kinds of message middleware. In order to realize the message forwarding of two message middleware clusters, the transmission configuration parameters of the two message middlewares can be obtained, and the message forwarding information can be generated through the transmission configuration parameters of the two message middlewares, and the two messages can be realized through the message forwarding information The long connection between the middleware, and then realize the information transmission of the message in the two message middleware through the long connection, and improve the transmission reliability of the message in the two different message middleware.

In the embodiment of the present application, the message forwarding information of the first message middleware and the second message middleware can be determined, and the message forwarding information is used to indicate the respective configuration parameters of the two message middlewares. Through the message forwarding information, it is possible to establish a relationship with The long connection between the first message middleware and the second message middleware realizes the use of electronic equipment as the transmission medium, respectively establishes long connections with the two message middleware, and then realizes the same transmission path between the two message middleware of establishment. Through this long connection, it is possible to receive and configure the first message sent by the first message middleware, and convert the first message into a second message according to the message format of the second message middleware, so that the second message is adapted to The second message middleware is used to send the second message to the second message middleware according to the long connection, so as to realize message transmission between different message middlewares and improve the stability of message transmission between different message middlewares.

The data transmission method provided in this application aims to solve the above technical problems in the prior art.

The technical solution of the present application and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below in conjunction with the accompanying drawings.

FIG. 1 shows a system architecture diagram for implementing a message forwarding method provided by an embodiment of the present application. The message forwarding system may include: a first message middleware cluster 11 , where a first message middleware 110 is configured in the first message middleware cluster 11 . An electronic device 12 connected to the first message middleware cluster 11 . The second message middleware cluster 13 connected to the electronic device 12, wherein the second message middleware 130 is configured in the second message middleware cluster 13 .

The first message middleware 110 may process messages requested to be sent or obtained by other nodes in the first message middleware cluster 11 . The second message middleware 130 may process messages requested to be sent or obtained by other nodes in the second message middleware cluster 13 .

The electronic device 12 may obtain message forwarding information of the first messaging middleware 110 and the second messaging middleware 130 , the message forwarding information including the transmission configuration of the first messaging middleware and the transmission configuration of the second messaging middleware. The electronic device 12 may establish a persistent connection with the first messaging middleware 110 and the second messaging middleware 130 respectively, so as to receive the first message sent by the first messaging middleware 110 based on the persistent connection. After the first message is converted into the second message according to the message format of the second message middleware, the second message may be sent to the second message middleware 130 according to the long connection.

FIG. 2 is a flow chart of an embodiment of a message forwarding method provided in an embodiment of the present application. The message forwarding method may be configured as a message forwarding device, and the message forwarding device may be located in an electronic device. The message forwarding method may include the following steps:

S201: Determine the message forwarding information corresponding to the first message middleware and the second message middleware, the first message middleware and the second message middleware are of different types, and the message forwarding information is used to indicate the first message middleware and the second message middleware file's respective transport configuration.

Optionally, the first message middleware may be IBMMQ, and the second message middleware may be TDMQ, or the first message middleware may be TDMQ, and the second message middleware may be IBMMQ. In addition, the first message middleware and the second message middleware may also be other types of message middleware, and the specific types of message middleware are not limited too much in this embodiment. The types of the first message middleware and the second message middleware only need to be different.

The message middleware can be any node in the server cluster, and the message provider in the server cluster can transmit the message to the node of the message middleware of its cluster, that is, to the message middleware. The message middleware can run on the nodes in the cluster, and the message middleware can receive or send the message. Specifically, the node where the message middleware is located can receive the message or send the message. Node, the second message middleware can be configured on the second node. A node may refer to a computing node in a server cluster that has functions such as data receiving and sending, and data processing. The first message middleware may directly send the first message to the electronic device through its first node. The second message middleware can receive the second message through its second node.

The message forwarding information may include the transmission configuration of the first messaging middleware and the transmission configuration of the second messaging middleware at the second node, specifically according to the transmission configuration information of the first node where the first messaging middleware is located and the transmission configuration of the first messaging middleware at the second node. The transmission configuration information of the second node is generated.

S202: Based on the message forwarding information, establish a persistent connection with the first message middleware and the second message middleware respectively.

Optionally, the message forwarding information may include the middleware identifier of the first messaging middleware and the middleware identifier of the second messaging middleware. The middleware identifier may be, for example, an access IP (Internet Protocol, Internet Protocol) address. A persistent connection with the first messaging middleware can be established through the middleware identifier of the first messaging middleware, and a persistent connection with the second messaging middleware can be established through the middleware identifier of the second messaging middleware. Long connections of the first message middleware and the second message middleware are respectively established, and a transmission path between the first message middleware and the second message middleware is established.

The long connection refers to maintaining the existence of the transmission path between the first message middleware and the second message middleware, specifically, it may be to establish a long connection between the electronic device and the first message middleware, and a long connection between the electronic device and the second message middleware .

S203: Receive the first packet sent by the first message middleware according to the long connection with the first message middleware.

The first message may be generated based on the message format supported by the first message middleware.

S204: Convert the first packet into the second packet according to the packet format of the second message middleware.

The second message may be generated according to the message format supported by the second message middleware.

S205: Send the second packet to the second message middleware according to the long connection with the second message middleware.

Optionally, step 205 may include: receiving a message pull request sent by the second message middleware; in response to the message pull request, sending the second message to the second message according to the long connection with the second message middleware middleware. The consumption of the second message by the second message middleware can be timed through the message pull request, and the effectiveness of message sending can be improved.

In the embodiment of the present application, the message forwarding information of the first message middleware and the second message middleware can be determined, and the message forwarding information is used to indicate the respective configuration parameters of the two message middlewares. Through the message forwarding information, it is possible to establish a relationship with The long connection between the first message middleware and the second message middleware realizes the use of electronic equipment as the transmission medium, respectively establishes long connections with the two message middleware, and then realizes the same transmission path between the two message middleware of establishment. Through this long connection, it is possible to receive and configure the first message sent by the first message middleware, and convert the first message into a second message according to the message format of the second message middleware, so that the second message is adapted to The second message middleware is used to send the second message to the second message middleware according to the long connection, so as to realize message transmission between different message middlewares and improve the stability of message transmission between different message middlewares.

Further, on the basis of any of the above embodiments, determining the message forwarding information corresponding to the first messaging middleware and the second messaging middleware includes:

Receive an activation request of the message forwarding service, where the activation request includes identification information of the first messaging middleware and identification information of the second messaging middleware;

In response to the start request, determine message forwarding information corresponding to the identification information of the first messaging middleware and/or the identification information of the second messaging middleware.

The identification information of the first messaging middleware may include information such as a middleware name and a middleware identifier of the first messaging middleware. The identification information of the second message middleware may include information such as a middleware name and a middleware identifier of the second message middleware. The identification information may be used to distinguish different message middleware, that is, the identification information of the first message middleware may be different from the identification information of the second message middleware.

The message forwarding service may be provided for users, that is, the electronic device may output message forwarding service startup prompt information, and may generate a startup request when detecting that the user performs a click operation on the startup prompt information. The identification information of several message middlewares may be displayed in the startup prompt information, and the identification information of the first message middleware and the identification information of the second message middleware selected by the user may be detected.

In this embodiment, an activation request of the message forwarding service may be received, and the activation request may include identification information of the first messaging middleware and identification information of the second messaging middleware. Message forwarding can be performed on two different types of message middleware through the start request, so as to realize the acquisition of message forwarding information. By responding to the start request in time, the message forwarding information corresponding to the first message middleware and the second message middleware can be obtained in time, so that the transmission path corresponding to the first message middleware and the second message middleware can be realized in time by using the message forwarding information Establishment, and then realize the stable transmission of messages.

As shown in FIG. 3 , the flow chart of another embodiment of a message forwarding method provided by the embodiment of the present application is different from the foregoing embodiments in that, before step 201, it may also include:

S301: Collect transmission configuration information corresponding to the first messaging middleware and transmission configuration information corresponding to the second messaging middleware.

S302: Generate message forwarding information according to the transmission configuration information corresponding to the first messaging middleware and the transmission configuration information corresponding to the second messaging middleware.

S303: Store the message forwarding information in a forwarding database.

Step 201: Determine the message forwarding information corresponding to the first message middleware and the second message middleware, which may specifically include:

S304: Query message forwarding information associated with the first message middleware and/or the second message middleware from the forwarding database.

Optionally, the message forwarding information may include the first forwarding information forwarded by the first messaging middleware to the second messaging middleware, and/or the message forwarding information may further include the first forwarding information forwarded by the second messaging middleware to the first messaging middleware. 2. Forward information. Both the first forwarding information and/or the second forwarding information may be generated through transmission configuration information of the first message middleware and transmission configuration information of the second middleware.

Wherein, the transmission configuration information of the first message middleware may include parameter values respectively corresponding to at least one first transmission parameter. The transmission configuration information of the second message middleware may include parameter values corresponding to at least one second transmission parameter. The parameter type and the number of parameters of the at least one first transmission parameter and the at least one second transmission parameter may be different.

Exemplarily, at least one transmission parameter of the transmission middleware is described by taking TDMQ as the first message middleware and IBMMQ as the second message middleware as examples.

At least one first transmission parameter may include: TDMQ cluster access ip, TDMQ subject access information, message encoding type of the first message middleware, subject access information may include, for example: cluster-id (route reflector), namespace, authtoken, At least one of TDMQ topic name, TDMQ subscription name and other information.

At least one second transmission parameter may include: IBMMQ queue manager name, IBMMQ queue manager ip, target IBMMQ sending queue or target IBMMQ receiving queue, and message encoding type of the second message middleware.

In addition, in addition to the transmission configuration information corresponding to the first message middleware and the transmission configuration information corresponding to the second message middleware, the message forwarding information may also include other information, such as the message encoding type and The message encoding type supported by the second message middleware.

For example, the message forwarding information from TDMQ to IBMMQ can be: TDMQ cluster access ip, TDMQ topic access information, message encoding type, IBMMQ queue manager name, IBMMQ queue manager ip, target IBMMQ sending queue.

For example, the message forwarding information from IBMMQ to TDMQ can be: TDMQ cluster access ip, TDMQ topic access information, message encoding type, IBMMQ queue manager name, IBMMQ queue manager ip, IBMMQ receiving queue.

Wherein, the message encoding type in the message forwarding information may include the message encoding type of the first message middleware and the message encoding type of the second message middleware.

Optionally, after the electronic device collects the transmission configuration information corresponding to the first message middleware and the transmission configuration information corresponding to the second message middleware, it may also display the transmission configuration information corresponding to the first message middleware and the second message on the display interface. The transmission configuration information corresponding to the middleware. Specifically, the configuration operations performed by the user on the transmission configuration information corresponding to the first message middleware and the transmission configuration information corresponding to the second message middleware may be detected, so as to obtain the transmission configuration information corresponding to the first message middleware configured by the user and the second message The transmission configuration information corresponding to the middleware. In addition, it may specifically include: reading the transmission configuration information from the first messaging middleware, and reading the transmission configuration information from the second messaging middleware. In addition, the transmission configuration information may also include message encoding types supported by the message middleware.

In the embodiment of the present application, the electronic device can collect the transmission configuration information of the first message middleware and the transmission configuration information of the second message middleware, and use the transmission configuration information corresponding to the first message middleware and the transmission configuration information of the second node, Message forwarding information may be generated. The message forwarding information can be stored in the forwarding database, that is, the pre-storage of the message forwarding information is completed, so that when there is a need for use, the message forwarding information associated with the first message middleware and/or the second message middleware can be quickly obtained, and the first message forwarding information can be improved. The establishment efficiency of the transmission path between the middleware and the second message middleware, and then the transmission of the two message middlewares can be carried out quickly and stably.

Further, on the basis of any of the above embodiments, the message forwarding information includes sending queue information of the first messaging middleware and receiving queue information of the second messaging middleware;

According to the long connection with the first message middleware, receive the first message sent by the first message middleware, including:

Pulling the first message from the sending queue corresponding to the sending queue information of the first messaging middleware according to the receiving thread corresponding to the long connection of the first messaging middleware;

According to the long connection with the second message middleware, the second message is sent to the second message middleware, including:

According to the sending thread corresponding to the persistent connection of the second messaging middleware, the second message is sent to the receiving queue corresponding to the receiving queue information of the second messaging middleware.

The receiving thread may be used to receive the first message of the first message middleware. The sending thread can be used to send the second message. By setting the receiving thread and sending thread, the independent execution of message receiving and message sending can be realized, and the efficiency of message receiving and sending can be improved.

In the embodiment of the present application, according to the receiving thread and sending thread corresponding to the persistent connection, the first message can be pulled through the sending queue, and the second message can be sent through the receiving queue. Realize the reception of the first message and the queue forwarding of the second message, and realize the stable and efficient forwarding of the message.

Further, on the basis of any of the above embodiments, converting the first message into the second message according to the message format of the second message middleware includes:

The first packet is parsed to obtain message content of the first packet.

Encapsulate the content of the message into the second message according to the message format of the second message middleware.

The message format may refer to a message data structure corresponding to a message encoding type supported by the second message middleware.

The message content may be specific information carried in the first packet.

In the embodiment of the present application, the message content of the first message is obtained by analyzing the first message, and the message content is encapsulated into the second message according to the message format of the second message middleware, so as to realize the The content conversion of a message to the second message enables the second message to be adapted to the second message middleware, ensures that the second message can be normally transmitted to the second message middleware, and ensures the compatibility of the two message middleware Stability and reliability of message forwarding.

Further, optionally, the first message is parsed to obtain the message content of the first message, including:

Analyzing the first message to obtain message content composed of a message header and a message body of the first message;

According to the message format of the second message middleware, the message content is encapsulated into the second message, including:

According to the message format of the second message middleware, determine the message header format and the message body format of the second message;

Determine the message header of the second message according to the message header format;

Converting the message body of the first message into the message body of the second message according to the message body format;

Encapsulate the message header of the second message and the message body of the second message to obtain the second message.

Optionally, message parsing refers to a process of parsing a message from one encoding method to another encoding method.

Exemplarily, the message may be encoded in a binary manner, and parsing the first message refers to dividing the first message into a message header and a message body, and dividing the binary character string of the message header and the binary character of the message body The strings are respectively converted into strings expressed in ASCII (American Standard Code for Information Interchange, American Standard Code for Information Interchange) code mode, and the message header and message body of the first message are obtained, which can be used as the message content .

Encapsulating the message header and message body of the second message may specifically refer to converting the message header and message body of the second message into a character string suitable for communication transmission. For example, the character string formed in ASCII mode is converted into binary code, and the obtained binary character string can be used as the second message.

In the embodiment of the present application, when the first message is repackaged into the second message, the message header and the message body of the first message can be correspondingly encapsulated into the message format corresponding to the second message middleware to realize The segmented encapsulation of the second message format ensures that the encapsulation of the second message is more reliable and effective.

Further, optionally, after parsing the first message and obtaining the message content composed of the message header and the message body of the first message, the method further includes:

Extracting the personalized information and other information in the message header of the first message;

According to the message header format, determine the message header of the second message, including:

Converting other information in the message header of the first message into the message header of the second message according to the message header format;

Convert the message body of the first message into the message body of the second message according to the message body format, including:

Convert the personalized information and the message body of the first message into the message body of the second message according to the message body format.

Personalized information may be personalized content set in the message header of the first packet, which may be set according to usage requirements. Adding personalized information to the message header of the first message can realize personalized transmission of the message and improve the flexibility of message transmission.

In this embodiment of the application, the message header of the first message may include personalized header information and other information, and for the personalized header information, it may be encapsulated as part of the message body into the second message In the message body, avoid the problem that the message encapsulation fails or the message encapsulation succeeds but does not match the actual format of the second message due to the incompatibility between the personalized information and the message header of the second message, and realizes the second The accurate encapsulation of the message improves the accurate encapsulation of the second message, and avoids encapsulation failure or error.

Further, on the basis of any of the above embodiments, according to the long connection with the first message middleware, after receiving the first message sent by the first message middleware, the method further includes:

Query whether the first message is associated with a message forwarding record from the record database. The record database is used to store message forwarding records corresponding to multiple messages. The message forwarding record includes the forwarding status of the message, and the forwarding status includes forwarded, not forwarded or forwarded. Forwarding failed;

If so, query the forwarding status in the message forwarding record associated with the first message;

If the forwarding state in the message forwarding record associated with the first message is forwarded, then delete the first message;

If the forwarding state in the message forwarding record associated with the first message is not forwarded, then execute converting the first message into a second message according to the message format of the second message middleware;

If the forwarding state in the message forwarding record associated with the first message is forwarding failure, return the first message to the first node corresponding to the first message middleware.

Optionally, deleting the first packet may refer to destroying the first packet. When the forwarding state of the first message is not forwarded, subsequent steps 204 and 205 may be performed to realize normal forwarding of the message.

In the embodiment of the present application, the message forwarding records corresponding to the multiple messages stored in the database may be recorded, and the message forwarding records are used to record the forwarding status of the messages. Whether there is a message forwarding record in the first message can be confirmed by querying the record database. And if there is a message forwarding record in the first message, confirm the forwarding state of the first message. And perform different processing in different forwarding states to achieve accurate and effective forwarding of the first message, avoid repeated forwarding, and return the first message to the first node when the forwarding fails, so as to timely forward the forwarding result Feedback to the first node to improve the forwarding efficiency and stability of the first message.

Further, optionally, after querying whether the first message is associated with a message forwarding record from the record database, it also includes:

If not, then according to the long connection with the second message middleware, after the second message is sent to the second message middleware, according to the forwarding state of the first message, generate a message forwarding record, a message forwarding record;

Store message forwarding records in a records database.

In this embodiment, when the message forwarding record of the first message is not found in the record database, the forwarding state of the first message can be used to generate the message forwarding record of the first message, and the message forwarding record of the first message can be Forwarding records are stored in a records database. After the second message is forwarded, the message forwarding record of the first message can be determined according to its forwarding status, so as to realize the timely storage of the message forwarding record, participate in the subsequent forwarding monitoring scene, and improve the effectiveness and efficiency of message forwarding. reliability.

Further, on the basis of any of the above embodiments, according to the long connection with the second message middleware, after sending the second message to the second message middleware, it also includes:

If the sending of the second message fails, push the first message to the dead letter queue;

Based on the timing compensation task, pull the first message that fails to be forwarded from the dead letter queue;

According to the message format of the second message middleware, the first message that fails to be forwarded is re-converted into a third message;

According to the long connection, the third packet is compensated and sent to the second node.

Optionally, the dead letter queue may be used to store at least one message whose transmission fails. If any message fails to be transmitted, the message can be pushed to the dead letter queue, and according to the timing compensation task, the message that fails to be forwarded is pulled from the dead letter queue to realize the retransmission of the message.

The timing compensation task refers to performing fixed frequency compensation based on the set compensation frequency. When the current time reaches the compensation time determined according to the compensation frequency, the first packets that fail to be forwarded can be pulled from the dead letter queue one by one, so as to re-execute the packet format conversion and compensation sending.

In the embodiment of the present application, when the sending of the second message fails, the first message may be pushed to the dead letter queue. The first message that failed to be transmitted can be stored in the dead letter queue, so that under the execution of the timing compensation task, the first message that failed to be forwarded can be pulled from the dead letter queue, so that the first message that failed to be pulled can be reprocessed. Message conversion and sending. Compensation and transmission can be performed on the first message that fails to be forwarded to improve the transmission success rate, thereby effectively improving the reliability of message forwarding by two different message middleware.

As shown in FIG. 4 , it is a schematic structural diagram of an embodiment of a message forwarding device provided in an embodiment of the present application, and the message forwarding device can implement any one of the above message forwarding methods. The message forwarding means may be located in the electronic device. Wherein, the message forwarding device 400 may include:

Determining unit 401: used to determine message forwarding information corresponding to the first message middleware and the second message middleware, the first message middleware and the second message middleware are of different types, and the message forwarding information is used to indicate the first message middleware and the second message middleware Respective configuration parameters of the second message middleware;

Establishing unit 402: for establishing a long connection with the first message middleware and the second message middleware respectively based on the message forwarding information;

The receiving unit 403: configured to receive the first message sent by the first message middleware according to the long connection with the first message middleware;

A conversion unit 404: configured to convert the first message into the second message according to the message format of the second message middleware;

Sending unit 405: configured to send the second packet to the second messaging middleware according to the long connection with the second messaging middleware.

Further, on the basis of any of the above embodiments, the determining unit includes:

The request receiving module is configured to receive an activation request of the message forwarding service, where the activation request includes identification information of the first messaging middleware and identification information of the second messaging middleware;

The request response module is configured to determine message forwarding information corresponding to the identification information of the first messaging middleware and/or the identification information of the second messaging middleware in response to the start request.

Further, on the basis of any of the above embodiments, it also includes:

A collection unit, configured to collect transmission configuration information corresponding to the first message middleware and transmission configuration information corresponding to the second message middleware;

A generating unit, configured to generate message forwarding information according to the transmission configuration information corresponding to the first message middleware and the transmission configuration information corresponding to the second message middleware;

a storage unit, configured to store message forwarding information in a forwarding database;

Identify units, including:

An information query module, configured to query message forwarding information associated with the first message middleware and/or the second message middleware from the forwarding database.

Further, on the basis of any of the above embodiments, the message forwarding information includes sending queue information of the first messaging middleware and receiving queue information of the second messaging middleware;

Receiver unit, including:

The message pulling module is used to pull the first message from the sending queue corresponding to the sending queue information of the first message middleware according to the receiving thread corresponding to the long connection of the first message middleware;

sending unit, consisting of:

The message sending module is configured to send the second message to the receiving queue corresponding to the receiving queue information of the second messaging middleware according to the sending thread corresponding to the long connection of the second messaging middleware.

Further, on the basis of any of the above embodiments, the converting unit includes:

A message parsing module, configured to parse the first message to obtain the message content of the first message;

The packet encapsulation module is configured to encapsulate the message content into the second packet according to the packet format of the second message middleware.

Further, on the basis of any of the above-mentioned embodiments, the message parsing module includes:

The message parsing sub-module is used for parsing the first message to obtain the message content composed of the message header and the message body of the first message;

Packet encapsulation module, including:

A format determining submodule, configured to determine the message header format and message body format of the second message according to the message format of the second message middleware;

The first determining submodule is used to determine the message header of the second message according to the format of the message header;

The second determining submodule is used to convert the message body of the first message into the message body of the second message according to the message body format;

The message determining submodule is configured to encapsulate the message header of the second message and the message body of the second message to obtain the second message.

Further, on the basis of any of the above embodiments, it also includes:

a personality extraction unit, configured to extract the personalized information and other information in the message header of the first message;

The first sub-module is determined, which can be specifically used for:

Converting other information in the message header of the first message into the message header of the second message according to the message header format;

The second determination sub-module can be specifically used for:

Convert the personalized information and the message body of the first message into the message body of the second message according to the message body format.

Further, on the basis of any of the above embodiments, it also includes:

The record query unit is used to query whether the first message is associated with a message forwarding record from the record database, and the record database is used to store message forwarding records corresponding to a plurality of messages respectively, the message forwarding record includes the forwarding status of the message, and the forwarding status includes forwarded, not forwarded or failed to forward;

The state query unit is used to obtain the forwarding state in the message forwarding record associated with the first message if it is true;

The first processing unit is configured to delete the first message if the forwarding state in the message forwarding record associated with the first message is forwarded;

The second processing unit is configured to convert the first message into the second message according to the message format of the second message middleware if the forwarding state in the message forwarding record associated with the first message is not forwarded;

The third processing unit is configured to return the first message to the first message middleware if the forwarding status in the message forwarding record associated with the first message is forwarding failure.

Further, on the basis of any of the above embodiments, it also includes:

The record generating unit is configured to, if not, generate a message forwarding record according to the forwarding state of the first message after the second message is sent to the second message middleware according to the long connection with the second message middleware, message forwarding record;

The record storage unit is used for storing the message forwarding record in the record database.

Further, on the basis of any of the above embodiments, it also includes:

a failure processing unit, configured to push the first message to the dead letter queue if the second message fails to be sent;

A timing processing unit, configured to pull the first message that fails to be forwarded from the dead letter queue based on the timing compensation task;

A reconversion unit, configured to reconvert the first message that failed to be forwarded into a third message according to the message format of the second message middleware;

The compensation sending unit is configured to send the third message compensation to the second message middleware according to the long connection.

Fig. 5 is a block diagram showing a node according to an exemplary embodiment, the device may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant wait.

Apparatus 500 may include one or more of the following components: processing component 502, memory 504, power supply component 506, multimedia component 508, audio component 510, input/output (I/O) interface 512, sensor component 514, and communication component 516.

The processing component 502 generally controls the overall operations of the device 500, such as those associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 502 may include one or more modules that facilitate interaction between processing component 502 and other components. For example, processing component 502 may include a multimedia module to facilitate interaction between multimedia component 508 and processing component 502 .

The memory 504 is configured to store various types of data to support operations at the device 500 . Examples of such data include instructions for any application or method operating on device 500, contact data, phonebook data, messages, pictures, videos, and the like. The memory 504 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

The power supply component 506 provides power to various components of the device 500 . Power components 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 500 .

The multimedia component 508 includes a screen that provides an output interface between the device 500 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or a swipe action, but also detect duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 508 includes a front camera and/or a rear camera. When the device 500 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.

The audio component 510 is configured to output and/or input audio signals. For example, the audio component 510 includes a microphone (MIC), which is configured to receive external audio signals when the device 500 is in operation modes, such as call mode, recording mode and voice recognition mode. Received audio signals may be further stored in memory 504 or sent via communication component 516 . In some embodiments, the audio component 510 also includes a speaker for outputting audio signals.

The I/O interface 512 provides an interface between the processing component 502 and a peripheral interface module. The peripheral interface module may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

Sensor assembly 514 includes one or more sensors for providing status detection of various aspects of device 500 . For example, the sensor component 514 can detect the open/closed state of the device 500, the relative positioning of components, such as the display and keypad of the device 500, the sensor component 514 can also detect a change in the position of the device 500 or a component of the device 500, the user Presence or absence of contact with device 500 , device 500 orientation or acceleration/deceleration and temperature change of device 500 . Sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. Sensor assembly 514 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 514 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

The communication component 516 is configured to facilitate wired or wireless communication between the apparatus 500 and other devices. The device 500 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 516 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, communication component 516 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, apparatus 500 may be programmed by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the methods described above.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as the memory 504 including instructions, which can be executed by the processor 520 of the device 500 to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

The present application provides an electronic device, including: a processor, and a memory connected to the processor in communication;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so as to implement the possible method in any one of the foregoing embodiments.

The present application provides a computer-readable storage medium. Computer-executable instructions are stored in the computer-readable storage medium. When executed by a processor, the computer-readable instructions are used to implement the method as possible in any embodiment.

The present application provides a computer program product, including a computer program. When the computer program is executed by a processor, the method as possible in any embodiment is implemented.

Other embodiments of the present application will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the application, these modifications, uses or adaptations follow the general principles of the application and include common knowledge or conventional technical means in the technical field not disclosed in the application . The specification and examples are to be considered exemplary only, with a true scope and spirit of the application indicated by the following claims.

It should be understood that the present application is not limited to the precise constructions which have been described above and shown in the accompanying drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (13)

1. A message forwarding method, characterized in that, comprising: Determine message forwarding information corresponding to the first message middleware and the second message middleware, the first message middleware and the second message middleware are of different types, and the message forwarding information is used to indicate that the first message middleware The respective transmission configurations of the middleware and the second message middleware; Establishing a long connection with the first message middleware and the second message middleware respectively based on the message forwarding information; Receive the first message sent by the first message middleware according to the long connection with the first message middleware; converting the first message into a second message according to the message format of the second message middleware; Send the second message to the second message middleware according to the long connection with the second message middleware. 2. The method according to claim 1, wherein the determining the message forwarding information corresponding to the first message middleware and the second message middleware comprises: Receive an activation request of the message forwarding service, where the activation request includes identification information of the first messaging middleware and identification information of the second messaging middleware; In response to the start request, determine message forwarding information corresponding to the identification information of the first messaging middleware and/or the identification information of the second messaging middleware. 3. The method according to claim 1 or 2, further comprising: Collecting transmission configuration information corresponding to the first messaging middleware and transmission configuration information corresponding to the second messaging middleware; generating the message forwarding information according to the transmission configuration information corresponding to the first messaging middleware and the transmission configuration information corresponding to the second messaging middleware; storing the message forwarding information in a forwarding database; The determining the message forwarding information corresponding to the first message middleware and the second message middleware includes: Querying message forwarding information associated with the first message middleware and/or the second message middleware from the forwarding database. 4. The method according to claim 1, wherein the message forwarding information includes sending queue information of the first messaging middleware and receiving queue information of the second messaging middleware; The receiving the first message sent by the first message middleware according to the long connection with the first message middleware includes: Pulling the first message from the sending queue corresponding to the sending queue information of the first messaging middleware according to the receiving thread corresponding to the long connection of the first messaging middleware; The sending the second message to the second message middleware according to the long connection with the second message middleware includes: Send the second message to the receiving queue corresponding to the receiving queue information of the second messaging middleware according to the sending thread corresponding to the persistent connection of the second messaging middleware. 5. The method according to claim 1, wherein converting the first message into a second message according to the message format of the second message middleware comprises: Analyzing the first packet to obtain message content of the first packet; Encapsulating the message content into the second message according to the message format of the second message middleware. 6. The method according to claim 5, wherein said parsing said first message to obtain the message content of said first message comprises: Analyzing the first message to obtain message content composed of a message header and a message body of the first message; According to the message format of the second message middleware, encapsulating the message content into the second message includes: Determine the message header format and message body format of the second message according to the message format of the second message middleware; Determine the message header of the second message according to the message header format; converting the message body of the first message into the message body of the second message according to the message body format; Encapsulate the message header of the second message and the message body of the second message to obtain the second message. 7. The method according to claim 6, wherein after analyzing the first message and obtaining the message content formed by the message header and the message body of the first message, further comprising: Extracting the personalized information and other information in the message header of the first message; The determining the message header of the second message according to the message header format includes: converting other information in the message header of the first message into the message header of the second message according to the message header format; The converting the message body of the first message into the message body of the second message according to the message body format includes: Converting the personalized information and the message body of the first message into the message body of the second message according to the message body format. 8. The method according to claim 1, characterized in that, after receiving the first message sent by the first message middleware according to the long connection with the first message middleware, further comprising: Query whether the first message is associated with a message forwarding record from the record database, the record database is used to store message forwarding records corresponding to a plurality of messages, the message forwarding record includes the forwarding status of the message, and the forwarding Status includes Forwarded, Not Forwarded, or Forwarded Failed; If so, obtain the forwarding status in the message forwarding record associated with the first message; If the forwarding state in the message forwarding record associated with the first message is forwarded, then delete the first message; If the forwarding state in the message forwarding record associated with the first message is not forwarded, perform converting the first message into a second message according to the message format of the second message middleware; If the forwarding state in the message forwarding record associated with the first message is forwarding failure, return the first message to the first message middleware. 9. The method according to claim 8, wherein after querying whether the first message is associated with a message forwarding record from the record database, further comprising: If not, after the second message is sent to the second message middleware according to the long connection with the second message middleware, the first message is generated according to the first message A message forwarding record of a message; storing the message forwarding record of the first message in the record database. 10. The method according to claim 1, characterized in that, after sending the second message to the second message middleware according to the long connection with the second message middleware, further comprising: : If the sending of the second message fails, pushing the first message to a dead letter queue; Based on the timing compensation task, pull the first message that fails to be forwarded from the dead letter queue; Reconverting the first message that failed to be forwarded into a third message according to the message format of the second message middleware; Send the third message compensation to the second message middleware according to the long connection. 11. A message forwarding device, characterized in that it comprises: A determining unit, configured to determine message forwarding information corresponding to the first message middleware and the second message middleware, where the types of the first message middleware and the second message middleware are different, and the message forwarding information is used to indicate the Respective configuration parameters of the first message middleware and the second message middleware; An establishing unit, configured to respectively establish a long connection with the first message middleware and the second message middleware based on the message forwarding information; a receiving unit, configured to receive the first message sent by the first message middleware according to the long connection with the first message middleware; A conversion unit, configured to convert the first message into a second message according to the message format of the second message middleware; A sending unit, configured to send the second message to the second message middleware according to the long connection with the second message middleware. 12. An electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; The processor executes the computer-implemented instructions stored in the memory to implement the method according to any one of claims 1-10. 13. A computer-readable storage medium, characterized in that computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to implement any one of claims 1 to 10 when executed by a processor the method described.