WO2021179156A1

WO2021179156A1 - Message processing method, device and system, and server

Info

Publication number: WO2021179156A1
Application number: PCT/CN2020/078554
Authority: WO
Inventors: 庞大伟
Original assignee: 深圳市欢太科技有限公司; Oppo广东移动通信有限公司
Priority date: 2020-03-10
Filing date: 2020-03-10
Publication date: 2021-09-16
Also published as: CN115039392A

Abstract

Disclosed are a message processing method, device and system, and a server. The method comprises: if a first message queue calling request sent by a client is received, converting the first message queue calling request into a second message queue calling request; generating, on the basis of the second message queue calling request and a designated calling interface, message queue calling data adapted to the designated calling interface; and calling, according to the designated calling interface and the message queue calling data, a target message queue engine to execute the second message queue calling request. Therefore, by means of protocol conversion, when a service party sends a message queue calling request on the basis of a client having a different protocol, the message queue calling request of the service party can still be adapted, thereby improving the flexibility and compatibility in the processing of messages transmitted by a message queue.

Description

Message processing method, device, system and server

Technical field

This application relates to the field of computer technology, and more specifically, to a message processing method, device, system, and server.

Background technique

A message can be understood as a unit of data transmitted between two computers, and a message queue can be understood as a container for storing messages during the transmission of messages. In related devices that provide message queue proxy services, they are all services provided for a single message queue, resulting in a lack of flexibility and compatibility in the processing of messages transmitted by the message queue.

Summary of the invention

In view of the above problems, this application proposes a message processing method, device, system and server to improve the above problems.

In a first aspect, this application provides a message processing method, the method includes: if a first message queue call request sent by a client is received, converting the first message queue call request into a second message queue call request The message interaction protocol corresponding to the second message queue call request and the first message queue call request is different; based on the second message queue call request and a specified call interface, a message that is adapted to the specified call interface is generated Message queue calling data; according to the designated calling interface and the message queue calling data, the target message queue engine is called to execute the second message queue calling request.

In a second aspect, the present application provides a message processing method applied to a message processing system, the message processing system includes a protocol processing device, a message logic implementation device, and a message queue engine bearing device, and the method includes: the protocol processing If the device receives the first message queue call request sent by the client, it converts the first message queue call request into a second message queue call request, the second message queue call request and the first message queue call request The corresponding message interaction protocols are different; the message logic implementation device generates message queue calling data adapted to the specified calling interface based on the second message queue calling request and the designated calling interface; the message queue engine bearing device is based on the The designated calling interface and the message queue calling data are described, and the target message queue engine is called to execute the second message queue calling request.

In a third aspect, the present application provides a message processing device, the device includes: a protocol analysis unit, configured to convert the first message queue calling request into a message queue calling request sent by a client The second message queue call request, the message interaction protocol corresponding to the second message queue call request and the first message queue call request is different; the call logic implementation unit is used to call the request based on the second message queue and specify The calling interface generates message queue calling data adapted to the designated calling interface; a message processing execution unit is used to call the target message queue engine to execute the second message according to the designated calling interface and the message queue calling data Queue call request.

In a fourth aspect, the present application provides a message processing system. The message processing system includes a protocol processing device, a message logic implementation device, and a message queue engine bearing device. The system includes: the protocol processing device for receiving To the first message queue call request sent to the client, the first message queue call request is converted into a second message queue call request, and the second message queue call request corresponds to the first message queue call request The message interaction protocol is different; the message logic implementation device is used to generate message queue calling data adapted to the designated calling interface based on the second message queue calling request and the designated calling interface; the message queue engine bearing device is used According to the designated calling interface and the message queue calling data, the target message queue engine is called to execute the second message queue calling request.

In a fifth aspect, the present application provides a server including one or more processors and a memory; one or more programs are stored in the memory and configured to be executed by the one or more processors, so The one or more programs are configured to perform the methods described above.

In a sixth aspect, the present application provides a computer-readable storage medium having program code executable by a processor, the program code causing the processor to execute the above-mentioned method.

In the message processing method, device, system and server provided by the present application, if the first message queue call request sent by the client is received, the message interaction protocol can be converted first to convert the first message queue call request Call requests for a second message queue with a different message interaction protocol, and then generate message queue call data adapted to the specified call interface based on the second message queue call request and a designated call interface, and then generate message queue call data adapted to the designated call interface according to the designated call interface and The message queue calls data, calls the target message queue engine to execute the second message queue call request, so that through protocol conversion, in the case where the business party sends the message queue call request based on the client with different message interaction protocol, The message queue call request of the business party can be identified, and the message queue call data is generated based on the public designated call interface, and then the second message queue call request is executed through the designated call interface, thereby improving the message queue transmission rate Flexibility and compatibility in processing.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

Figure 1 shows a schematic diagram of an application scenario of a message processing method proposed in this application;

Figure 2 shows a schematic diagram of the application architecture of a message processing method proposed in this application;

FIG. 3 shows a schematic diagram of the application architecture of another message processing method proposed by this application;

Figure 4 shows a flow chart of a message processing method proposed by this application;

Figure 5 shows a flowchart of yet another message processing method proposed by this application;

Figure 6 shows a flowchart of yet another message processing method proposed by this application;

FIG. 7 shows a flowchart of another message processing method proposed by this application;

FIG. 8 shows a flowchart of yet another message processing method proposed by this application;

FIG. 9 shows a structural block diagram of a message processing method device proposed by this application;

FIG. 10 shows a structural block diagram of another message processing method and apparatus proposed by this application;

FIG. 11 shows a structural block diagram of another message processing method and device proposed by this application;

FIG. 12 shows a structural block diagram of another message processing method and device proposed by this application;

Fig. 13 shows a structural block diagram of an electronic device proposed in this application.

Fig. 14 is a storage unit for storing or carrying program code for implementing the message processing method according to the embodiment of the present application according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application. Messages can be regarded as objective material movement or subjective thinking activities, as well as a reflection of the state of the occurrence of events. It is described in detail through different forms such as language, text, images, and data. Messages can also be understood as interactions between software objects. And a way of communication.

For messages, they can be processed based on a message queue (Message Queue). Among them, the message queue can be compared to a container for storing messages. When you need to use the message, you can take out the message from the message queue for your own use. The message queue is a typical representative of the consumer-producer model. One end continuously writes messages to the message queue, while the other end can read the messages in the queue. The message publisher only publishes the message to the message queue regardless of who gets it, and the message consumer only gets the message from the message queue regardless of who publishes it.

In addition, the message queue is an important component in a distributed system, and the use of message queues can improve system performance, peak clipping, and reduce system coupling through asynchronous processing. Message queues can have ActiveMQ, RabbitMQ, Kafka, RocketMQ and other types, but different message queues use different message exchange protocols. Among them, the message interaction protocol can be understood as a protocol for message interaction between the message queue client and the message queue agent server.

The inventor’s research on the process of processing messages in related message queues found that in related devices that provide message queue proxy services, they are all services provided for a single message queue, resulting in the processing of messages transmitted by the message queue. It still lacks a certain degree of flexibility and compatibility. Exemplarily, in related message processing methods, the message queue server usually only recognizes the message queue call request sent by a message queue client that uses an inherent message interaction protocol, while other message interaction protocols are used. The message queue call request sent by the client cannot be recognized normally, resulting in poor versatility and compatibility of the message queue proxy server. In addition, in this case, in order to adapt to the client that adopts the inherent message interaction protocol, it may be necessary to separately and completely deploy a set of message queue proxy server, which will increase the overall cost.

Therefore, in order to improve the above problems, the inventor proposed the message processing method, device, system and server in this application. The method provided in this application can at least perform the message first after receiving the first message queue call request sent by the client. The conversion of the interaction protocol to convert the first message queue call request into a second message queue call request with a different message interaction protocol, and then based on the second message queue call request and a specified call interface, generate a call interface with the specified call interface The adapted message queue calls data, and then calls the target message queue engine to execute the second message queue call request according to the specified call interface and the message queue call data, so that through protocol conversion, the business side is based on the message When a client with a different interaction protocol sends a message queue call request, it can still identify the message queue call request of the business party, and then generate the message queue call data based on the public designated call interface, and then execute the message queue call data through the designated call interface The second message queue calls the request, thereby improving the flexibility and compatibility in the processing of messages transmitted by the message queue. The following first introduces the environment of a message processing system in which the message processing method and device provided in this application run.

As shown in FIG. 1, the message processing system 100 shown in FIG. 1 includes a protocol analysis unit, a call logic implementation unit, and a message processing execution unit.

Among them, the protocol analysis unit is used to perform protocol identification and conversion on the message queue request sent by the message queue client, so that the purpose of calling the message queue by the message queue client can be identified. For example, if the first message queue call request sent by the client is received in this application, the first message queue call request can be converted into the second message queue call request.

The calling logic implementation unit is used to generate message queue calling data adapted to the designated calling interface according to the public designated calling interface and the converted second queue calling request. Among them, the protocol analysis unit can obtain at least one actual logic call data from metadata viewing, metadata creation, message sending, and message consumption after the protocol conversion. The call logic implementation unit will obtain the data according to the public designated call interface and the conversion. The actual call data is generated, and the message queue call data adapted to the specified call interface is generated. It should be noted that the common designated call interface means that no matter what message interaction protocol is used by the message queue client to generate a message queue call request, and no matter which message queue engine is actually used to execute the message queue call request, it is Based on the specified call interface.

The message processing execution unit is configured to call the target message queue engine to execute the second message queue calling request according to the designated calling interface and the message queue calling data. It should be noted that a variety of message queue engines can be encapsulated in the message processing execution unit, and the target message queue engine refers to the message queue engine currently responsible for executing the message queue call request among the various message queue engines. .

In one manner, the protocol analysis unit, the calling logic implementation unit, and the message processing execution unit may be deployed in the same hardware device (for example, a server), and in addition, they may also be deployed in different hardware devices. Optionally, the protocol analysis unit is deployed in the first hardware device, the calling logic implementation unit is deployed in the second hardware device, and the message processing execution unit is deployed in the third hardware device. In this case, the first hardware device can be regarded as a protocol processing device, the second hardware device can be regarded as a message logic implementation device, and the third hardware device can be understood as a message queue engine bearing device.

In another way, the protocol parsing unit and the calling logic implementation unit can be deployed in the same hardware device, and the message processing execution unit can be in a single step in a hardware device. Furthermore, the multiple message queue engines encapsulated in the message processing execution unit may be separately partly in one hardware device.

Exemplarily, as shown in FIG. 2, the hardware device 121 carries a message proxy service, and the hardware device 131, the hardware device 132, and the hardware device 133 each carry a message queue engine. In this case, the hardware device 121 runs with The aforementioned protocol analysis unit and call logic implementation unit, and the hardware device 131, the hardware device 132, and the hardware device 133 each carry a message processing execution unit. In this case, the hardware device 121 that carries the message proxy service can call any one of the hardware device 131, the hardware device 132, and the hardware device 133 based on the network address of the message queue as needed to execute the data sent by the client 10. Message queue call request. Furthermore, as another way, in order to increase the reliability of the message queue proxy service, the message queue proxy service can be a service cluster, as shown in Figure 3, multiple message queue proxy services can be configured, for example, in Figure 3 The message queue proxy service 121 and the message queue proxy service 122 of the message queue proxy service 122. In this case, the message queue call request of the same client 10 can be sent by the message queue proxy service 121 and the message queue proxy service 122 under different circumstances. One for processing. For example, when the message queue proxy service 121 is unavailable, the message queue proxy service 122 may process the message queue call request of the client 10. Correspondingly, when the hardware device 132 is unavailable, the message queue agent service 122 in the hardware device 131 or the hardware device 133 can be switched to execute the message queue request. Hereinafter, each embodiment of the present application will be described in detail with reference to the accompanying drawings.

Please refer to FIG. 4, a message processing method provided by this application, the method includes:

S110: If the first message queue calling request sent by the client is received, the first message queue calling request is converted into a second message queue calling request, and the second message queue calling request is the same as the first message queue calling request. The message exchange protocol corresponding to the request is different. In this embodiment, the client can be understood as a client running the Message Queuing SDK, and the client running the Message Queuing SDK can be deployed on the business side.

It should be noted that in this implementation, subsequent generation of message queue call data is generated based on the message queue call request of the same protocol. In this case, if the message exchange protocol based on the first message queue call request sent by the client is different from the same protocol, the message exchange protocol will be converted first to change the first message originally sent by the client The queue call request is converted into a second message queue call request based on the same protocol. Exemplarily, if the message queue proxy service provided in this embodiment is executed, the subsequent message queue call data generation is performed based on the message interaction protocol A. Then, when it is recognized that the first message queue call request sent by the client is based on message interaction protocol B, the first message queue call request based on message interaction protocol B will undergo protocol conversion and be converted to message interaction protocol based A's first message queue call request. For another example, when it is recognized that the first message queue call request sent by the client is based on message interaction protocol C, the first message queue call request based on message interaction protocol C will also be converted to message-based The first message queue of the interactive protocol A calls the request.

S120: Based on the second message queue calling request and the designated calling interface, generate message queue calling data adapted to the designated calling interface.

It should be noted that in this embodiment, the message queue engine that actually executes the message queue call request will be encapsulated, and after the encapsulation is completed, the data interface will be configured so that the message queue engine can be actually called through the data interface, and then in this case In the embodiment, in order to complete the actual message queue call, it is necessary to generate message queue call data in the form of a data interface, and the data interface can be understood as the aforementioned designated call interface.

S130: According to the designated calling interface and the message queue calling data, call the target message queue engine to execute the second message queue calling request.

In this embodiment, after the message queue call data is generated, the message queue call data can be input to a designated call interface, and then the target message queue engine is called through the designated call interface to execute the second message queue call request. Among them, it should be noted that when the client sends a message queue call request, it is actually preparing to process the message through the message queue. The processing of this message can be understood as sending information to other clients or extracting information sent by other clients. In this case, calling the target message queue engine through the designated call interface to execute the second message queue call request can be understood as calling the target message queue engine through the designated call interface to perform information transmission or information extraction. .

Exemplarily, if the first message queue call request sent by the client characterizes information A to other clients through the message queue, the corresponding second message queue request after protocol conversion also characterizes information A Send to other clients, then when the target message queue engine executes the second message queue call request, it characterizes the actual process of sending information A.

In the message processing method provided by the embodiment of the present application, if the first message queue call request sent by the client is received, the message interaction protocol conversion may be performed first, so as to convert the first message queue call request into the message interaction protocol Different second message queue call requests, and then based on the second message queue call request and the designated call interface, generate message queue call data adapted to the designated call interface, and then according to the designated call interface and the message queue Call the data, call the target message queue engine to execute the second message queue call request, so that by means of protocol conversion, the business party can still be identified when the message queue call request is sent by the client based on different message interaction protocols. And then generate message queue calling data based on the public designated calling interface, and then execute the second message queue calling request through the designated calling interface, thereby improving the flexibility in the processing of messages transmitted by the message queue Sex and compatibility.

Please refer to FIG. 5, a message processing method provided by this application, the method includes:

S210: If the first message queue calling request sent by the client is received, obtain the protocol adopted by the first message queue calling request. It can be understood that the protocol used by the first message queue call request refers to the message interaction protocol used, and in this embodiment, there may be multiple ways to obtain the protocol used by the first message queue call request.

As a way, the client's own identifier can be used to identify the protocol used by the message queue request sent by the device. In this way, a mapping table between the client's identity and the protocol used by the corresponding message queue request can be established in advance, and then when the first message queue request sent by the client is obtained, the client's identity can be directly identified, and then the The client's identifier searches the mapping table for the protocol used by the corresponding message queue request. Wherein, the identification of the client can be a network address. As another way, the data format of the message queue request sent by the client can be analyzed to identify the corresponding protocol.

S220: Based on the adopted protocol, convert the first message queue call request into a second message queue call request based on the target protocol, and the second message queue call request is the same as the first message queue call request. The corresponding message exchange protocol is different.

As a way, the converting the first message queue call request to the second message queue call request based on the target protocol based on the adopted protocol includes: calling and calling the second message queue based on the adopted protocol. The conversion plug-in adapted to the first message queue call request converts the first message queue call request into a second message queue call request based on the target protocol.

It should be noted that, as a way, a variety of conversion plug-ins can be configured in the message queue proxy service running the message processing method provided in this embodiment, which corresponds to the message interaction protocol that each client may use. Correspondingly, a conversion plug-in is configured, and the multiple conversion plug-ins can convert the message queue call request based on different message interaction protocols into the message queue call request based on the subsequent generation of the message queue call data. Exemplarily, a conversion plug-in A, a conversion plug-in B, a conversion plug-in C, and a conversion plug-in D may be configured in the message queue proxy service. In one case, the message processing method provided in this embodiment generates message queue call data based on the message queue call request using protocol F (that is, the aforementioned target protocol). In this case, the conversion plug-in A can be configured In order to convert the first message queue call request based on protocol A into the second message queue call request based on protocol F, the conversion plug-in B can be configured to convert the first message queue call request based on protocol B into the second message queue call request based on protocol F Message queue call request, conversion plug-in C can be configured to convert the first message queue call request based on protocol C to the second message queue call request based on protocol F, and conversion plug-in D can be configured to convert the first message based on protocol D The queue call request is converted into a second message queue call request based on protocol F.

As a result, when a new message interaction protocol is launched through plug-ins, it is only necessary to configure the corresponding conversion plug-in for the newly online message interaction protocol, instead of modifying the message queue agent service as a whole, which improves the message queue. The efficiency of agency service upgrades.

As a way, based on the adopted protocol, the conversion plug-in adapted to the first message queue call request is called to convert the first message queue call request into a second message queue call based on the target protocol Before the request, it also includes: detecting whether the first message queue has been loaded to call the requested conversion plug-in; if the first message queue has been loaded, calling the requested conversion plug-in, executing the protocol based on the adopted protocol Invoke a conversion plug-in adapted to the first message queue call request to convert the first message queue call request into a second message queue call request based on the target protocol.

If the first message queue calls the adapted conversion plug-in that is not loaded, search the plug-in storage area for the first message queue to call the adapted conversion plug-in through the plug-in manager; if the first message queue is found, call The conversion plug-in that requests the adaptation is dynamically loaded to the first message queue to call the conversion plug-in that is requested to be adapted, and after the dynamic loading is completed, the conversion plug-in that is adapted to the first message queue call request is called to transfer the The first message queue call request is converted into the second message queue call request based on the target protocol.

As a way, you can configure a storage area to store the identity of the loaded conversion plug-in. In this way, by traversing the storage area where the identity of the loaded conversion plug-in is stored, you can get the currently loaded Conversion plug-in.

S230: Based on the second message queue calling request and the designated calling interface, generate message queue calling data adapted to the designated calling interface. The message queue invocation data includes various parameters needed to actually invoke the message queue service through the designated invocation interface, and the format and composition of the various parameters are adapted to the designated invocation interface. Optionally, the multiple parameters may include the request purpose of the second message queue request obtained by converting the protocol (for example, information transmission or information reading), and the message processing object (for example, information to be sent or information to be read) Wait.

S240: According to the designated calling interface and the message queue calling data, call the target message queue engine to execute the second message queue calling request. As a way, the method provided in this embodiment further includes: during initialization, acquiring the conversion plug-in stored in the plug-in storage area. It should be noted that the initialization can be understood as the initialization of the message queue proxy service provided by this embodiment at startup. Optionally, during initialization, updating the conversion plug-in stored in the plug-in storage area includes: during initialization, obtaining the conversion plug-in stored in the plug-in storage area, and storing the conversion plug-in in the plug-in storage area. The conversion plug-in of is compared with the conversion plug-in stored in the management terminal, and if the inconsistent conversion plug-in is compared, the inconsistent conversion plug-in is obtained and registered, and the registered conversion plug-in is stored in the plug-in storage area. It should be noted that the plug-in storage area here is a different storage area from the aforementioned storage area storing the identifier of the loaded conversion plug-in. The plug-in storage area here can be understood as a pooled plug-in storage area.

The message processing method provided by the embodiment of the present application can still identify the message queue calling request of the business party through protocol conversion when the business party sends a message queue calling request based on clients with different message interaction protocols. In addition, the message queue calling data is generated based on the public designated calling interface, and then the second message queue calling request is executed through the designated calling interface, thereby improving the flexibility and compatibility in the processing of messages transmitted by the message queue. Moreover, in the process of protocol conversion in this embodiment, the conversion plug-in corresponding to the message queue used by the client is called to perform the conversion of the call request, so that the client that supports the new message interaction protocol is online. In the case of, just develop the corresponding conversion plug-in for the newly launched client, without updating the overall architecture, which further improves the flexibility of the message queue agent service upgrade.

Please refer to FIG. 6, a message processing method provided by this application, the method includes: S310: If a first message queue call request sent by a client is received, obtain the byte stream corresponding to the first message queue call request . S320: Identify the protocol adopted by the first message queue call request based on the byte stream. As a way, the identification of the protocol used for the first message queue call request based on the byte stream includes: obtaining the byte stream format of the byte stream corresponding to the first message queue call request; The byte stream format is matched with multiple reference byte stream formats; the protocol corresponding to the reference byte stream format matching the byte stream format is used as the protocol adopted by the first message queue call request. As a way, after the client establishes communication with the message queue proxy service that executes the message processing method through a long connection, the message queue proxy service can start to obtain the first message queue call request sent by the client The first message queue calls the byte stream corresponding to the request, and at the same time identifies the byte stream format of the byte stream corresponding to the first message queue call request, and then calls the obtained byte stream corresponding to the first message queue call request The byte stream format of is sent to multiple conversion plug-ins, so that multiple conversion plug-ins will perform internal matching with reference to the byte stream format. If it is detected that a conversion plug-in returns information that the matching is successful, it represents the conversion plug-in that feedbacks the successful matching information The corresponding reference byte stream format matches the byte stream format of the byte stream corresponding to the first message queue call request, and the protocol corresponding to the reference byte stream format corresponding to the conversion plug-in is used as the first message queue The protocol used by the call request.

It should be noted that the reference byte stream format corresponding to the conversion plug-in can be understood as the byte stream format corresponding to the protocol that can be converted. Exemplarily, the conversion plug-in B may be configured to convert the first message queue call request based on protocol B into the second message queue call request based on protocol F, then the reference byte stream format corresponding to the conversion plug-in B is protocol B The corresponding byte stream format. The byte stream format corresponding to the protocol can be understood as the format of the byte stream in the transmission process of the message queue call request generated based on the protocol.

As a way, after identifying the byte stream format of the byte stream corresponding to the first message queue call request, it can be directly cached in the corresponding long connection, so that subsequent message queue call requests under the same long connection can be The actual protocol used can be obtained without the aforementioned protocol identification, which improves the efficiency of message queue calling.

S330: Based on the adopted protocol, convert the first message queue call request into a second message queue call request based on the target protocol, and the second message queue call request is the same as the first message queue call request. The corresponding message exchange protocol is different.

S340: Based on the second message queue calling request and the designated calling interface, generate message queue calling data adapted to the designated calling interface.

S350: According to the designated calling interface and the message queue calling data, call the target message queue engine to execute the second message queue calling request.

The message processing method provided by the embodiment of the present application can determine the message interaction protocol adopted by the first message queue call request based on the byte stream corresponding to the first message queue call request, so that through protocol conversion, the business side When clients with different message interaction protocols send message queue call requests, they can still identify the message queue call request of the business party, and then generate message queue call data based on the public designated call interface, and then execute it through the designated call interface The second message queue calls the request, thereby improving the flexibility and compatibility in the processing of messages transmitted by the message queue.

Please refer to FIG. 7, a message processing method provided by the present application, the method includes: S410: Select a first message queue engine from a plurality of candidate message queue engines as the target message queue engine. S420: If the first message queue calling request sent by the client is received, the first message queue calling request is converted into a second message queue calling request, and the second message queue calling request is the same as the first message queue calling request. The message exchange protocol corresponding to the request is different.

S430: Based on the second message queue calling request and the designated calling interface, generate message queue calling data adapted to the designated calling interface.

S440: According to the designated calling interface and the message queue calling data, call the target message queue engine to execute the second message queue calling request.

Optionally, the method provided in this embodiment further includes: if it is detected that the first message queuing engine is in a designated state, using a second message queuing engine of the plurality of message queuing engines to be selected as the target message Queuing engine.

As a way, the designated state includes when the first message queuing engine is in a state to be upgraded; if it is detected that the first message queuing engine is in the designated state, the selected state of the message queuing engine is selected As the target message queuing engine, the second message queuing engine includes:

If it is detected that the first message queuing engine is in the to-be-upgrade state, the second message queuing engine among the plurality of message queuing engines to be selected is used as the target message queuing engine.

Furthermore, as another way, the designated state includes when the first message queuing engine is in a message sending blocking state; if it is detected that the first message queuing engine is in the designated state, the multiple The second message queuing engine in the message queuing engine to be selected as the target message queuing engine includes: if it is detected that the first message queuing engine is in a message sending blocking state, the first message queuing engine among the plurality of message queuing engines to be selected 2. The message queuing engine serves as the target message queuing engine.

Thus, the entire message queue proxy service is in a highly available state through the aforementioned switching of the target message queue engine.

Optionally, the multiple message queuing engines to be selected are all plug-in message queuing engines.

The message processing method provided by the embodiment of the present application can determine the message interaction protocol adopted by the first message queue call request based on the byte stream corresponding to the first message queue call request, so that through protocol conversion, the business side When clients with different message interaction protocols send message queue call requests, they can still identify the message queue call request of the business party, and then generate message queue call data based on the public designated call interface, and then execute it through the designated call interface The second message queue calls the request, thereby improving the flexibility and compatibility in the processing of messages transmitted by the message queue. In addition, in this embodiment, the target message queue engine can be flexibly selected from multiple candidate message queue engines, which improves the stability of the message queue call request processing.

Please refer to FIG. 8, a message processing method provided by this application, the method includes:

S510: Perform security verification on the client that sends the first message queue call request.

S520: If the security verification succeeds, when the first message queue invocation request sent by the client is received, the first message queue invocation request is converted into the second message queue invocation request. The message interaction protocol corresponding to the second message queue call request and the first message queue call request is different.

S530: Based on the second message queue calling request and the designated calling interface, generate message queue calling data adapted to the designated calling interface.

S540: According to the designated calling interface and the message queue calling data, call the target message queue engine to execute the second message queue calling request.

The message processing method provided by the embodiment of the application can still identify the message queue calling request of the business party when the business party sends a message queue calling request based on clients with different message interaction protocols, and then based on the common designated calling The interface generates message queue call data, and then executes the second message queue call request through the designated call interface, thereby improving the flexibility and compatibility in the processing of messages transmitted by the message queue. In addition, in this embodiment, the target message queue engine can be flexibly selected from multiple candidate message queue engines, which improves the stability of the message queue call request processing. In addition, in this embodiment, the client that sends the first message queue call request will also perform security verification first, which improves the security of the message queue proxy service.

Referring to FIG. 9, a message processing apparatus 600 provided by the present application includes: a protocol analysis unit 610, configured to: if a first message queue call request sent by a client is received, the first message queue The call request is converted into a second message queue call request, and the message interaction protocol corresponding to the second message queue call request and the first message queue call request are different. The calling logic implementation unit 620 is configured to generate message queue calling data adapted to the designated calling interface based on the second message queue calling request and the designated calling interface. The message processing execution unit 630 is configured to call the target message queue engine to execute the second message queue calling request according to the designated calling interface and the message queue calling data. As a way, the protocol parsing unit 610 is specifically configured to obtain the protocol adopted by the first message queue calling request if the first message queue calling request sent by the client is received; based on the adopted protocol, The first message queue calling request is converted into a second message queue calling request based on the target protocol. In this manner, optionally, the protocol parsing unit 610 is specifically configured to call a conversion plug-in adapted to the first message queue call request to transfer the first message queue call request based on the adopted protocol. Converted to the second message queue call request based on the target protocol.

In this manner, the protocol parsing unit 610 is also specifically configured to detect whether the first message queue calls the conversion plug-in requesting adaptation has been loaded; if the first message queue calls the conversion plug-in requesting adaptation has been loaded, Execute the protocol based on the adopted, and call a conversion plug-in adapted to the first message queue call request to convert the first message queue call request into a second message queue call request based on the target protocol. And it is also specifically used to search for the conversion plug-in adapted to the first message queue call request in the plug-in storage area through the plug-in manager if the conversion plug-in adapted to the first message queue call request is not loaded; if the conversion plug-in is found The first message queue calls the conversion plug-in that requests the adaptation, dynamically loads the conversion plug-in that the first message queue calls the request for adaptation, and after the dynamic loading is completed, calls the conversion plug-in that is adapted to the first message queue call request The conversion plug-in converts the first message queue call request into a second message queue call request based on the target protocol. Correspondingly, as shown in FIG. 10, the device 600 further includes: a conversion plug-in management unit 640, configured to update the conversion plug-ins stored in the plug-in storage area during initialization. As a way, the conversion plug-in management unit 640 is specifically configured to obtain conversion plug-ins stored in the plug-in storage area during initialization; and convert the conversion plug-ins stored in the plug-in storage area to the conversion stored in the management terminal. The plug-ins are compared; if the inconsistent conversion plug-ins are compared, the inconsistent conversion plug-ins are obtained and registered; and the registered conversion plug-ins are stored in the plug-in storage area.

As a way, the protocol analysis unit 610 is specifically configured to obtain the byte stream corresponding to the first message queue call request; and identify the protocol adopted by the first message queue call request based on the byte stream. In this manner, the protocol parsing unit 610 is specifically configured to obtain the byte stream format of the byte stream corresponding to the first message queue call request; compare the byte stream format with multiple reference byte stream formats Matching; the protocol corresponding to the reference byte stream format matching the byte stream format is used as the protocol adopted by the first message queue call request.

As a way, as shown in FIG. 11, the device 600 further includes: a message queue engine management unit 650, configured to select the first message queue engine from a plurality of candidate message queue engines as the target message queue engine . Optionally, the message queuing engine management unit 650 is specifically configured to use a second message queuing engine of the plurality of message queuing engines to be selected as the target if it is detected that the first message queuing engine is in a designated state Message queue engine.

Optionally, the specified state includes when the first message queue engine is in a state to be upgraded. In this case, the message queuing engine management unit 650 is specifically configured to, if it is detected that the first message queuing engine is in the to-be-upgraded state, set the second message queuing engine of the plurality of message queuing engines to be selected as The target message queue engine. Furthermore, optionally, the specified state includes when the first message queuing engine is in a message sending blocking state. In this case, the message queuing engine management unit 650 is specifically configured to detect the first message When the queuing engine is in the message sending blocking state, the second message queuing engine among the multiple to-be-selected message queuing engines is used as the target message queuing engine.

Optionally, the multiple message queuing engines to be selected are all plug-in message queuing engines. As a manner, as shown in FIG. 12, the device 600 further includes: a security verification unit 660, configured to perform security verification on the client that sends the first message queue call request. In this manner, the protocol analysis unit 610 is configured to, if the security verification succeeds, execute the first message queue call request sent by the client, and convert the first message queue call request to a second message queue. Message queue call request.

In the message processing device provided by the present application, if the first message queue calling request sent by the client is received, the message interaction protocol conversion may be performed first, so as to convert the first message queue calling request into a message interaction protocol with a different first message interaction protocol. 2. A message queue call request, and then based on the second message queue call request and a designated call interface, generate message queue call data adapted to the designated call interface, and then call data according to the designated call interface and the message queue , Call the target message queue engine to execute the second message queue call request, so that through protocol conversion, the message queue call request of the business party can still be identified when the business party sends a message queue call request based on a client with a different message interaction protocol Queue call request, and then generate message queue call data based on the public designated call interface, and then execute the second message queue call request through the designated call interface, thereby improving the flexibility in the processing of messages transmitted by the message queue and compatibility.

Hereinafter, an electronic device provided by the present application will be described with reference to FIG. 13.

Referring to FIG. 10, based on the foregoing short message pushing method, an embodiment of the present application also provides another electronic device 200 including a processor 102 that can execute the foregoing short message pushing method. The electronic device 200 further includes a memory 104 and a network module 106. Wherein, the memory 104 stores a program that can execute the content in the foregoing embodiment, and the processor 102 can execute the program stored in the memory 104.

Among them, the processor 102 uses various interfaces and lines to connect various parts of the entire electronic device 200, by running or executing instructions, programs, code sets, or instruction sets stored in the memory 104, and calling data stored in the memory 104 , Perform various functions of the electronic device 200 and process data. Optionally, the processor 102 may use at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). A kind of hardware form to realize. The processor 102 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a modem, and the like. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is used for rendering and drawing of display content; the modem is used for processing wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 102, but may be implemented by a communication chip alone.

The memory 104 may include random access memory (RAM) or read-only memory (Read-Only Memory). The memory 104 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 104 may include a storage program area and a storage data area, where the storage program area may store instructions for implementing the operating system and instructions for implementing at least one function (such as touch function, sound playback function, image playback function, etc.) , Instructions used to implement the following various method embodiments, etc. The data storage area can also store data (such as phone book, audio and video data, chat record data) created by the terminal 100 during use.

The network module 106 is used to receive and send electromagnetic waves, and realize the mutual conversion between electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices, such as with an audio playback device. The network module 106 may include various existing circuit elements for performing these functions, for example, an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a subscriber identity module (SIM) card, a memory, etc. . The network module 106 can communicate with various networks, such as the Internet, an intranet, and a wireless network, or communicate with other devices through a wireless network. The aforementioned wireless network may include a cellular telephone network, a wireless local area network, or a metropolitan area network. For example, the network module 106 can exchange information with the base station.

Optionally, the electronic device 200 may be a server that executes the foregoing method embodiments.

Please refer to FIG. 14, which shows a structural block diagram of a computer-readable storage medium provided by an embodiment of the present application. The computer-readable medium 1100 stores program code, and the program code can be invoked by a processor to execute the method described in the foregoing method embodiment.

The computer-readable storage medium 1100 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, hard disk, or ROM. Optionally, the computer-readable storage medium 1100 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 1100 has a storage space for executing the program code 810 of any method step in the above-mentioned method. These program codes can be read from or written into one or more computer program products. The program code 1110 may be compressed in an appropriate form, for example.

To sum up, in the message processing method, device, system and server provided by this application, if the first message queue call request sent by the client is received, the message exchange protocol can be converted first to convert the first message queue. The message queue call request is converted into a second message queue call request with a different message interaction protocol, and then based on the second message queue call request and the specified call interface, the message queue call data adapted to the specified call interface is generated, and then according to all The designated calling interface and the message queue calling data are called, the target message queue engine is called to execute the second message queue calling request, and the message queue calling request is sent on the business side based on the client with different message interaction protocols by means of protocol conversion. Under the circumstance, the message queue call request of the business party can still be identified, and the message queue call data is generated based on the public designated call interface, and then the second message queue call request is executed through the designated call interface, thereby improving the message Flexibility and compatibility in the processing of messages transmitted by the queue.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the foregoing embodiments are modified, or some of the technical features thereof are equivalently replaced; these modifications or replacements do not drive the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A message processing method, characterized in that the method includes:

If the first message queue call request sent by the client is received, the first message queue call request is converted into a second message queue call request. The second message queue call request is the same as the first message queue call request. The corresponding message exchange protocol is different;

Based on the second message queue calling request and the designated calling interface, generating message queue calling data adapted to the designated calling interface;

According to the designated calling interface and the message queue calling data, the target message queue engine is called to execute the second message queue calling request.
The method according to claim 1, wherein the converting the first message queue calling request to the second message queue calling request if the first message queue calling request sent by the client is received includes:

If the first message queue calling request sent by the client is received, acquiring the protocol adopted by the first message queue calling request;

Based on the adopted protocol, the first message queue call request is converted into a second message queue call request based on the target protocol.
The method according to claim 2, wherein the converting the first message queue call request into a second message queue call request based on the target protocol based on the adopted protocol comprises:

Based on the adopted protocol, a conversion plug-in adapted to the first message queue call request is invoked to convert the first message queue call request into a second message queue call request based on the target protocol.
The method according to claim 3, characterized in that, based on the adopted protocol, a conversion plug-in adapted to the first message queue call request is called to convert the first message queue call request to a Before the call request of the second message queue of the target protocol, it also includes:

Detecting whether the conversion plug-in requested by the first message queue has been loaded;

If the first message queue call request adaptation conversion plug-in has been loaded, execute the protocol based on the adopted and call the conversion plugin adapted to the first message queue call request to transfer the first message queue The call request is converted into a second message queue call request based on the target protocol.
The method according to claim 4, wherein the method further comprises:

If the conversion plug-in requested by the first message queue is not loaded, search for the conversion plug-in requested by the first message queue in the plug-in storage area through the plug-in manager;

If the conversion plug-in requested by the first message queue is found, the first message queue is dynamically loaded and the conversion plug-in requested by the request is dynamically loaded, and after the dynamic loading is completed, the first message queue is called The conversion plug-in adapted to the call request converts the first message queue call request into a second message queue call request based on the target protocol.
The method according to claim 5, wherein the method further comprises:

During initialization, the conversion plug-in stored in the plug-in storage area is updated.
7. The method according to claim 6, wherein, during initialization, updating the conversion plug-in stored in the plug-in storage area comprises:

During initialization, obtain the conversion plug-in stored in the plug-in storage area;

Comparing the conversion plug-in stored in the plug-in storage area with the conversion plug-in stored in the management terminal;

If inconsistent conversion plug-ins are compared, obtain and register the inconsistent conversion plug-ins;

And store the registered conversion plug-in in the plug-in storage area.
The method according to any one of claims 2-7, wherein said obtaining the protocol used by the first message queue call request comprises:

Acquiring the byte stream corresponding to the first message queue call request;

Identify the protocol adopted by the first message queue call request based on the byte stream.
The method according to claim 8, wherein the identifying a protocol adopted by the first message queue call request based on the byte stream comprises:

Acquiring the byte stream format of the byte stream corresponding to the first message queue call request;

Matching the byte stream format with multiple reference byte stream formats;

The protocol corresponding to the reference byte stream format matching the byte stream format is used as the protocol adopted by the first message queue invocation request.
The method according to any one of claims 1-9, wherein the method further comprises:

Select the first message queuing engine from a plurality of candidate message queuing engines as the target message queuing engine.
The method according to claim 10, wherein the method further comprises:

If it is detected that the first message queuing engine is in a designated state, the second message queuing engine among the multiple to-be-selected message queuing engines is used as the target message queuing engine.
The method according to claim 11, wherein the designated state includes when the first message queuing engine is in a state to be upgraded; if it is detected that the first message queuing engine is in a designated state, the The second message queuing engine among the plurality of message queuing engines to be selected as the target message queuing engine includes:

If it is detected that the first message queuing engine is in the to-be-upgrade state, the second message queuing engine among the plurality of message queuing engines to be selected is used as the target message queuing engine.
The method according to claim 11, wherein the designated state includes when the first message queuing engine is in a message sending blocking state; if it is detected that the first message queuing engine is in a designated state, the The second message queuing engine of the plurality of message queuing engines to be selected as the target message queuing engine includes:

If it is detected that the first message queuing engine is in a message sending blocking state, the second message queuing engine among the multiple to-be-selected message queuing engines is used as the target message queuing engine.
The method according to any one of claims 10-13, wherein the plurality of message queuing engines to be selected are all plug-in message queuing engines.
The method according to any one of claims 1-14, wherein if the first message queue call request sent by the client is received, the first message queue call request is converted into a second message queue call request It also included:

Performing security verification on the client that sent the first message queue call request;

If the security verification is successful, execute if the first message queue invoking request sent by the client is received, converting the first message queue invoking request into a second message queue invoking request.
A message processing method, characterized in that it is applied to a message processing system, the message processing system includes a protocol processing device, a message logic implementation device, and a message queue engine bearing device, and the method includes:

If the protocol processing device receives the first message queue call request sent by the client, it converts the first message queue call request into a second message queue call request, and the second message queue call request is the same as the first message queue call request. The message interaction protocol corresponding to the message queue call request is different;

The message logic implementation device generates message queue calling data adapted to the designated calling interface based on the second message queue calling request and the designated calling interface;

The message queue engine bearing device calls the target message queue engine to execute the second message queue calling request according to the designated calling interface and the message queue calling data.
A message processing device, characterized in that the device includes:

The protocol analysis unit is configured to convert the first message queue calling request into a second message queue calling request if the first message queue calling request sent by the client is received, and the second message queue calling request is the same as the first message queue calling request. A message exchange protocol corresponding to a message queue call request is different;

A call logic implementation unit, configured to generate message queue call data adapted to the specified call interface based on the second message queue call request and the specified call interface;

The message processing execution unit is configured to call the target message queue engine to execute the second message queue calling request according to the designated calling interface and the message queue calling data.
A message processing system, characterized in that, the message processing system includes a protocol processing device, a message logic implementation device, and a message queue engine bearing device, and the system includes:

The protocol processing device is configured to convert the first message queue calling request into a second message queue calling request if the first message queue calling request sent by the client is received, and the second message queue calling request is related to the The message interaction protocol corresponding to the first message queue call request is different;

The message logic implementation device is configured to generate message queue call data adapted to the specified call interface based on the second message queue call request and a specified call interface;

The message queue engine bearing device is used to call the target message queue engine to execute the second message queue calling request according to the designated calling interface and the message queue calling data.
A server, characterized in that it includes one or more processors and a memory;

One or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the method according to any one of claims 1-15.
A computer-readable storage medium having program code executable by a processor, wherein the program code causes the processor to execute the method according to any one of claims 1-15.