A message management method, system, computer device, and storage medium

Abstract

The present invention relates to a message management method, system, computer equipment, and storage medium, and the key points of its technical solution are: the method includes: pre-defining the business end according to the encoding of the message body to obtain a message data structure; matching the event code with several business ends, and establishing several subscription rules; receiving the message body and event code sent by the sending business end; matching the corresponding receiving business end according to the event code; processing the message body according to the message data structure of the receiving business end to obtain a corresponding subscription message; sending the corresponding subscription message to the corresponding receiving business end according to the subscription rule corresponding to the event code; the application has the advantages of reducing the complexity of calls between business services and reducing the depth of service link calls.

Description

Technical Field

[0001] The present invention relates to the technical field of message management, and more specifically, to a message management method, system, computer equipment, and storage medium. Background Art

[0002] Usually in traditional monolithic applications, all businesses are in the same application environment, so business transactions are easy to handle. However, after the business is split into different services, the problem that arises is how each business transaction exchanges information.

[0003] In the currently popular microservice environment, most business transactions are conducted through HTTP interfaces or dubbo rpc, etc. This also leads to the interlacing of links between business services, increasing the complexity of the system. The problem of a business service calling link is very deep, so there is still room for improvement. Summary of the invention

[0004] In view of the deficiencies in the prior art, the purpose of the present invention is to provide a message management method, system, computer device, and storage medium, which have the advantages of reducing the complexity of calls between business services and reducing the depth of service link calls.

[0005] The above technical objectives of the present invention are achieved through the following technical solutions: A message management method, comprising:

[0006] Define the business end in advance according to the encoding of the message body to obtain the message data structure; match the event code with several business ends, and establish several subscription rules;

[0007] Receive the message body and event code sent by the sending business end;

[0008] Match the corresponding receiving service end according to the event code;

[0009] Process the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message;

[0010] According to the subscription rule corresponding to the event code, the corresponding subscription message is sent to the corresponding receiving service end.

[0011] Optionally, the business end is defined in advance according to the encoding of the message body to obtain a message data structure, including:

[0012] Pre-set the encoding of the message body corresponding to the business end;

[0013] Obtain the corresponding message according to the encoding of the message body;

[0014] Convert the message into a message data structure that matches the service end.

[0015] Optionally, the processing of the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message includes:

[0016] The message body is split according to the encoding of the message body to obtain split messages;

[0017] Matching the receiving service end with the split message to obtain a matching message;

[0018] The matching message is converted according to the message data structure to obtain a subscription message corresponding to the receiving service end.

[0019] Optionally, converting the matching message according to the message data structure to obtain a subscription message corresponding to the receiving service end includes:

[0020] Match the variable object in the message data structure with the keyword of the matching message;

[0021] The message corresponding to the keyword of the matching message is converted based on the attribute of the variable object to obtain the subscription message corresponding to the receiving service end.

[0022] Optionally, sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code includes:

[0023] Find the corresponding receiving service end according to the subscription rule corresponding to the event code;

[0024] Each subscription message is sent to the corresponding receiving service end according to the encoding of each subscription message.

[0025] Optionally, after sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code, the method further includes:

[0026] Monitor and receive the reply message sent by the business end;

[0027] The sending status of the subscription message is identified according to the reply message; the sending status includes sending success, sending failure and the reason for failure.

[0028] Optionally, after sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code, the method further includes:

[0029] The subscription message corresponding to the event code is stored.

[0030] A message management system, comprising:

[0031] The data definition module is used to pre-define the business end according to the encoding of the message body to obtain the message data structure; match the event code with several business ends and establish several subscription rules;

[0032] The data receiving module is used to receive the message body and event code sent by the sending service end;

[0033] A port matching module, used to match the corresponding receiving service end according to the event code;

[0034] A message generation module, used to process the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message;

[0035] The message push module is used to send the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code.

[0036] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0037] A computer-readable storage medium stores a computer program, which implements the steps of the above method when executed by a processor.

[0038] In summary, the present invention has the following beneficial effects: the business end subscribes to messages from the platform end through event codes. After receiving the message body and the event code, the platform end analyzes the message body to convert the message body into a converted message body, and then cleans the converted message body according to the event code configuration, so that the message in the converted message body corresponds to the event code configuration, and generates a rule message body, and the platform end stores the rule message body in a database; the platform end pushes the rule message body to the business end according to the corresponding event code to complete the message delivery. Since the conversion of each message body is completed on the platform end, the business end only needs to subscribe to the corresponding message from the platform end, and the platform end can push the message that meets the event code subscription rule to the business end for consumption, so its call link level is shallow. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 It is a schematic diagram of the process of the present invention;

[0040] Figure 2 It is a structural schematic diagram of the present invention;

[0041] Figure 3 1 is a diagram showing the internal structure of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION

[0042] In order to make the purpose, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are described in detail below in conjunction with the accompanying drawings. Several embodiments of the present invention are shown in the accompanying drawings. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein.

[0043] In the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal connection of two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances. The terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features.

[0044] In the present invention, unless otherwise clearly specified and limited, the first feature being "above" or "below" the second feature may include the first and second features being in direct contact, or may include the first and second features being in contact not directly but through another feature between them. Moreover, the first feature being "above", "above" and "above" the second feature includes the first feature being directly above and obliquely above the second feature, or simply indicates that the first feature is higher in level than the second feature. The first feature being "below", "below" and "below" the second feature includes the first feature being directly below and obliquely below the second feature, or simply indicates that the first feature is lower in level than the second feature. The terms "vertical", "horizontal", "left", "right", "above", "below" and similar expressions are for illustrative purposes only, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention.

[0045] The present invention is described in detail below in conjunction with the accompanying drawings and embodiments.

[0046] The present invention provides a message management method, such as Figure 1 As shown, including:

[0047] Step 100: pre-define the service end according to the encoding of the message body to obtain the message data structure; match the event code with several service ends, and establish several subscription rules;

[0048] Step 200: Receive the message body and event code sent by the sending service end;

[0049] Step 300: Match the corresponding receiving service end according to the event code;

[0050] Step 400: Process the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message;

[0051] Step 500: Send the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code.

[0052] In actual applications, a message platform is constructed according to the message management method. The following takes the application of the message platform in the e-commerce industry as an example. First, the business end of the e-commerce industry is divided into merchant end, client end and warehouse end. The merchant end, client end and warehouse end respectively define message data results and subscription rules with the message platform. After the customer places an order through the client, the client generates a corresponding order message body and a corresponding order event code. The message platform receives the order event code and the order message body, matches the corresponding merchant end according to the order event code, and processes the message data structure of the order message body so that the message data structure of the order message body conforms to the message data structure of the merchant end, thereby obtaining a subscription message. The message platform sends the subscription message to the corresponding merchant end to complete the message management. Since the business end only needs to subscribe to the corresponding message from the platform end, the platform end can push the message body that conforms to the event code subscription rule to the business end for consumption, so its call link level is shallow.

[0053] Furthermore, the service end is defined in advance according to the encoding of the message body to obtain a message data structure, including:

[0054] Pre-set the encoding of the message body corresponding to the business end;

[0055] Obtain the corresponding message according to the encoding of the message body;

[0056] Convert the message into a message data structure that matches the service end.

[0057] In actual applications, each code in the message body can correspond to each message message respectively, so the same message body can be converted into different message messages; for example, the message body of the goods shipped out from the warehouse needs to be sent to the client and the merchant, so two codes can be defined in the message body. The message message corresponding to code 201 matches the client, and the message message corresponding to code 201 is converted to make the message conform to the message data structure of the client, and the message message corresponding to code 202 matches the merchant, and the message message corresponding to code 202 is converted to make the message conform to the message data structure of the merchant.

[0058] The optional processing of the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message includes:

[0059] The message body is split according to the encoding of the message body to obtain split messages;

[0060] Matching the receiving service end with the split message to obtain a matching message;

[0061] The matching message is converted according to the message data structure to obtain a subscription message corresponding to the receiving service end.

[0062] In actual applications, taking the warehouse end sending a message body and event code as an example, the warehouse end is the sending business end; since there are multiple codes in the message body, the message body is split into a message message coded as 201, a message message coded as 202, and messages corresponding to other codes, and then the message message coded as 201 is matched with the client, and the message message coded as 202 is matched with the merchant end to obtain a matching message corresponding to the client and a matching message corresponding to the merchant end; then the matching message corresponding to the client is converted according to the message data structure agreed upon with the client to obtain a subscription message corresponding to the client; the matching message corresponding to the merchant end is converted according to the message data structure agreed upon with the merchant end to obtain a subscription message corresponding to the merchant end.

[0063] Optionally, converting the matching message according to the message data structure to obtain a subscription message corresponding to the receiving service end includes:

[0064] Match the variable object in the message data structure with the keyword of the matching message;

[0065] The message corresponding to the keyword of the matching message is converted based on the attribute of the variable object to obtain the subscription message corresponding to the receiving service end.

[0066] In actual applications, a message event is a code that defines a string type and carries a json message corresponding to the code. This message is also called a business message, and the data structure is uncertain. By subscribing to the corresponding event code and the json message associated with the event code, different business services are realized based on the same event code, consumed according to the agreed data structure, and then different business logics are processed, so as to achieve the purpose of message exchange and business processing between the platform end and various business ends based on this message event.

[0067] Further, sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code includes:

[0068] Find the corresponding receiving service end according to the subscription rule corresponding to the event code;

[0069] Each subscription message is sent to the corresponding receiving service end according to the encoding of each subscription message.

[0070] In practical applications, the event code is equivalent to a bridge for multiple business terminals that agree to communicate. Data is transmitted to each business terminal through the same event code. For example, the warehouse terminal sends any event code, and the corresponding merchant terminal and client terminal are defined in the event code, so the merchant terminal and the client terminal are the receiving business terminals. The subscription rule of the event code is to send the subscription message of the merchant terminal to the merchant terminal, and the subscription message of the client terminal to the client terminal.

[0071] Further, after sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code, it also includes:

[0072] Monitor and receive the reply message sent by the business end;

[0073] The sending status of the subscription message is identified according to the reply message; the sending status includes sending success, sending failure and the reason for failure.

[0074] In actual applications, the message platform monitors the sending status of each rule message body, and can view the message source and message consumption through the platform. It can also add or delete the binding relationship between the event code and the business end through the platform, realizing the visualization functions of message event management, monitoring, query, and processing.

[0075] Further, after sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code, it also includes:

[0076] The subscription message corresponding to the event code is stored.

[0077] In actual applications, the event codes that have been sent and their corresponding subscription messages are stored in the cloud. Therefore, when searching on the merchant side, client side or warehouse side, the corresponding subscription message can be quickly retrieved according to the event code and sent to the corresponding business side again. Each business side can choose to delete the subscription message associated with itself.

[0078] like Figure 2 As shown, the present invention also provides a message management system, comprising:

[0079] The data definition module 10 is used to pre-define the service end according to the encoding of the message body to obtain the message data structure; match the event code with several service ends, and establish several subscription rules;

[0080] The data receiving module 20 is used to receive the message body and event code sent by the sending service end;

[0081] A port matching module 30, used for matching a corresponding receiving service end according to the event code;

[0082] A message generation module 40, used to process the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message;

[0083] The message push module 50 is used to send the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code.

[0084] Furthermore, the data definition module 10 includes:

[0085] The encoding definition unit is used to pre-set the encoding of the message body corresponding to the business end;

[0086] A message acquisition unit, used to acquire a corresponding message message according to the encoding of the message body;

[0087] The structure conversion unit is used to convert the message packet into a message data structure that matches the service end.

[0088] Furthermore, the message generation module 40 includes:

[0089] A message splitting unit, used for splitting the message body according to the encoding of the message body to obtain split messages;

[0090] A message matching unit, used for matching the receiving service end with the split message to obtain a matching message;

[0091] The message conversion unit is used to convert the matching message according to the message data structure to obtain a subscription message corresponding to the receiving service end.

[0092] Furthermore, the message conversion unit includes:

[0093] A keyword matching unit, used for matching the variable object in the message data structure with the keyword of the matching message;

[0094] The keyword conversion unit is used to convert the message corresponding to the keyword of the matching message based on the attribute of the variable object to obtain the subscription message corresponding to the receiving service end.

[0095] Furthermore, the message pushing module 50 includes:

[0096] A receiving search unit, used to search for a corresponding receiving service end according to a subscription rule corresponding to the event code;

[0097] The message sending unit is used to send each subscription message to the corresponding receiving service end according to the encoding of each subscription message.

[0098] Furthermore, the system further comprises:

[0099] A reply monitoring module is used to monitor the reply message sent by the receiving service end;

[0100] The status identification module is used to identify the sending status of the subscription message according to the reply message; the sending status includes successful sending, failed sending and the reason for failure.

[0101] Furthermore, the system further comprises:

[0102] The event storage module is used to store the subscription message corresponding to the event code.

[0103] For the specific definition of a message management system, please refer to the definition of a message management method above, which will not be repeated here. Each module in the above-mentioned message management system can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0104] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 3 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. When the computer program is executed by the processor, a message management method is implemented.

[0105] Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0106] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: a platform side defines an event code;

[0107] The platform and business sides define the message data structure based on the event code;

[0108] Define the business end in advance according to the encoding of the message body to obtain the message data structure; match the event code with several business ends, and establish several subscription rules;

[0109] Receive the message body and event code sent by the sending business end;

[0110] Match the corresponding receiving service end according to the event code;

[0111] Process the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message;

[0112] According to the subscription rule corresponding to the event code, the corresponding subscription message is sent to the corresponding receiving service end.

[0113] In one embodiment, the service end is defined in advance according to the encoding of the message body to obtain the message data structure, including:

[0114] Pre-set the encoding of the message body corresponding to the business end;

[0115] Obtain the corresponding message according to the encoding of the message body;

[0116] Convert the message into a message data structure that matches the service end.

[0117] In one embodiment, the processing of the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message includes:

[0118] The message body is split according to the encoding of the message body to obtain split messages;

[0119] Matching the receiving service end with the split message to obtain a matching message;

[0120] The matching message is converted according to the message data structure to obtain a subscription message corresponding to the receiving service end.

[0121] In one embodiment, converting the matching message according to the message data structure to obtain a subscription message corresponding to the receiving service end includes:

[0122] Match the variable object in the message data structure with the keyword of the matching message;

[0123] The message corresponding to the keyword of the matching message is converted based on the attribute of the variable object to obtain the subscription message corresponding to the receiving service end.

[0124] In one embodiment, sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code includes:

[0125] Find the corresponding receiving service end according to the subscription rule corresponding to the event code;

[0126] Each subscription message is sent to the corresponding receiving service end according to the encoding of each subscription message.

[0127] In one embodiment, after sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code, the method further includes:

[0128] Monitor and receive the reply message sent by the business end;

[0129] The sending status of the subscription message is identified according to the reply message; the sending status includes sending success, sending failure and the reason for failure.

[0130] In one embodiment, after sending the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code, the method further includes:

[0131] The subscription message corresponding to the event code is stored.

[0132] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0133] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0134] The above is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above embodiments. All technical solutions under the concept of the present invention belong to the protection scope of the present invention. It should be pointed out that for ordinary technicians in this technical field, some improvements and modifications without departing from the principle of the present invention should also be regarded as the protection scope of the present invention.

Claims

1. A message management method, characterized in that: include: Define the business end in advance according to the encoding of the message body to obtain the message data structure; Match event codes with several business terminals and establish several subscription rules; The service end is defined in advance according to the encoding of the message body to obtain the message data structure, including: Pre-set the encoding of the message body corresponding to the business end; Obtain the corresponding message according to the encoding of the message body; Convert the message into a message data structure that matches the service end; Receive the message body and event code sent by the sending business end; Match the corresponding receiving service end according to the event code; The message body is processed according to the message data structure of the receiving service end to obtain a corresponding subscription message; the message body is processed according to the message data structure of the receiving service end to obtain a corresponding subscription message, including: The message body is split according to the encoding of the message body to obtain split messages; Matching the receiving service end with the split message to obtain a matching message; The matching message is converted according to the message data structure to obtain a subscription message corresponding to the receiving service end; the matching message is converted according to the message data structure to obtain a subscription message corresponding to the receiving service end, including: Match the variable object in the message data structure with the keyword of the matching message; Based on the attributes of the variable object, the message corresponding to the keyword of the matching message is converted to obtain a subscription message corresponding to the receiving service end; A message event is a code that defines a string type and carries a JSON message corresponding to the code. This message subscribes to the corresponding event code and the JSON message associated with the event code to realize different business services based on the same event code, consume according to the agreed data structure, and then process different business logics, so as to achieve the purpose of message exchange and business processing between the platform end and various business ends based on this message event. Sending a corresponding subscription message to a corresponding receiving service end according to a subscription rule corresponding to the event code; sending the corresponding subscription message to a corresponding receiving service end according to a subscription rule corresponding to the event code includes: Find the corresponding receiving service end according to the subscription rule corresponding to the event code; Send each subscription message to the corresponding receiving service end according to the encoding of each subscription message; Store the subscription message corresponding to the event code; Monitor and receive the reply message sent by the business end; The sending status of the subscription message is identified according to the reply message; the sending status includes sending success, sending failure and the reason for failure.

2. A message management system, characterized in that: include: The data definition module is used to pre-define the business end according to the encoding of the message body to obtain the message data structure; Match the event code with several business terminals and establish several subscription rules; the business terminal is defined in advance according to the encoding of the message body to obtain the message data structure, including: Pre-set the encoding of the message body corresponding to the business end; Obtain the corresponding message according to the encoding of the message body; Convert the message into a message data structure that matches the service end; The data receiving module is used to receive the message body and event code sent by the sending service end; A port matching module, used to match the corresponding receiving service end according to the event code; A message generation module is used to process the message body according to the message data structure of the receiving service end to obtain a corresponding subscription message; the message body is processed according to the message data structure of the receiving service end to obtain a corresponding subscription message, including: The message body is split according to the encoding of the message body to obtain split messages; Matching the receiving service end with the split message to obtain a matching message; The matching message is converted according to the message data structure to obtain a subscription message corresponding to the receiving service end; the matching message is converted according to the message data structure to obtain a subscription message corresponding to the receiving service end, including: Match the variable object in the message data structure with the keyword of the matching message; Based on the attributes of the variable object, the message corresponding to the keyword of the matching message is converted to obtain a subscription message corresponding to the receiving service end; A message event is a code that defines a string type and carries a JSON message corresponding to the code. This message subscribes to the corresponding event code and the JSON message associated with the event code to realize different business services based on the same event code, consume according to the agreed data structure, and then process different business logics, so as to achieve the purpose of message exchange and business processing between the platform end and various business ends based on this message event. A message push module is used to send the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code; the sending of the corresponding subscription message to the corresponding receiving service end according to the subscription rule corresponding to the event code includes: Find the corresponding receiving service end according to the subscription rule corresponding to the event code; Send each subscription message to the corresponding receiving service end according to the encoding of each subscription message; Store the subscription message corresponding to the event code; Monitor and receive the reply message sent by the business end; The sending status of the subscription message is identified according to the reply message; the sending status includes sending success, sending failure and the reason for failure.

3. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to claim 1 are implemented.

4. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to claim 1 are implemented.

Images