Message processing method and apparatus, device, medium, and product

Abstract

A message processing method, executed by a first terminal device. The method comprises: displaying a message notification setting interface, the message notification setting interface being configured for setting a notification method for a service system (S301); in response to a first setting operation, setting notification method configuration information for the service system, the notification method configuration information being used for indicating M1 notification methods, and M1 being a positive integer (S302); and when a first notification message of the service system is received, outputting the first notification message by means of the set M1 notification methods (S303).

Description

Message processing methods, apparatus, equipment, media and products

[0001] Related applications

[0002] This application claims priority to Chinese patent application filed on February 19, 2025, with application number 202510185439.4 and entitled "Message Processing Method, Apparatus, Device, Medium and Product", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of computer technology, specifically to a message processing method, a message processing device, a computer equipment, a computer-readable storage medium, and a computer program product. Background Technology

[0004] With the deepening of globalization, cross-regional businesses (i.e., businesses whose execution involves at least two regions, such as cross-regional e-commerce, cross-regional asset transfer, and cross-regional logistics) have flourished in various industries in recent years, seeking greater development opportunities. Due to their geographical scope, the execution cycle of these business processes is typically long. Therefore, sending business process-related notification messages to business stakeholders in these scenarios can help them understand the specific business processes in a timely manner.

[0005] Currently, the methods for sending notification messages to business objects in business scenarios are often quite limited. This limited notification method may cause business objects to miss messages, resulting in poor message notification effectiveness. Summary of the Invention

[0006] This application provides a message processing method, apparatus, device, medium, and product.

[0007] On one hand, embodiments of this application provide a message processing method, executed by a first terminal device, the method comprising:

[0008] Displays the message notification settings interface, which is used to configure the notification method for the business system.

[0009] In response to the first setting operation, the notification method configuration information for the business system is set. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer.

[0010] When the first notification message is received from the business system, the first notification message is output in the M1 configured notification methods.

[0011] On one hand, embodiments of this application provide a message processing method, executed by a second terminal device, the method comprising:

[0012] The message notification management interface is displayed. The message notification management interface is used to perform notification management operations on the business system. The notification management operations include the second setting operation.

[0013] In response to the second setting operation, the notification message configuration information of the business system is set; the notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system; the notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer.

[0014] According to the notification message configuration information of the business system, send notification messages to the business objects in the business system.

[0015] On one hand, embodiments of this application provide a message processing method, executed by a server, the method comprising:

[0016] Obtain notification method configuration information for the business system from the first terminal device. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer.

[0017] The notification message configuration information of the business system is obtained from the second terminal device. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method. M2 is a positive integer.

[0018] Based on the notification method configuration information and notification message configuration information, the first notification message in the business system is encapsulated and processed.

[0019] The encapsulated first notification message is sent to the first terminal device for output.

[0020] On one hand, embodiments of this application provide a message processing apparatus, the apparatus comprising:

[0021] The display unit is used to display the message notification settings interface, which is used to set the notification method for the business system.

[0022] The processing unit is used to respond to the first setting operation by setting notification method configuration information for the business system. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer.

[0023] The output unit is used to output the first notification message in one of the M1 configured notification methods when the first notification message is received from the business system.

[0024] On one hand, embodiments of this application provide a message processing apparatus, the apparatus comprising:

[0025] The display unit is used to display the message notification management interface, which is used to perform notification management operations on the business system. The notification management operations include the second setting operation.

[0026] The processing unit is used to respond to the second setting operation and set the notification message configuration information of the business system. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer.

[0027] The sending unit is used to send notification messages to business objects in the business system according to the notification message configuration information of the business system.

[0028] On one hand, embodiments of this application provide a message processing apparatus, the apparatus comprising:

[0029] The acquisition unit is used to acquire notification method configuration information for the business system from the first terminal device. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer.

[0030] The acquisition unit is also used to acquire notification message configuration information of the business system from the second terminal device. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer.

[0031] The processing unit is used to encapsulate and process the first notification message in the business system based on the notification method configuration information and the notification message configuration information.

[0032] The sending unit is used to send the encapsulated first notification message to the first terminal device for output.

[0033] On one hand, embodiments of this application provide a computer device, including: a memory and a processor;

[0034] A memory, wherein one or more computer programs are stored;

[0035] A processor is used to load one or more computer programs to implement the message processing method described above.

[0036] On one hand, embodiments of this application provide a computer-readable storage medium storing a computer program adapted to be loaded by a processor and executed by the above-described message processing method.

[0037] On one hand, embodiments of this application provide a computer program product, which includes a computer program adapted to be loaded by a processor and execute the message processing method described above.

[0038] Details of one or more embodiments of this application are set forth in the following drawings and description. Other features, objects, and advantages of this application will become apparent from the specification, drawings, and claims. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the published drawings without creative effort.

[0040] Figure 1 is a schematic diagram of the architecture of a message processing system provided in an embodiment of this application;

[0041] Figure 2 is a three-terminal interaction flowchart of a message processing method provided in an embodiment of this application;

[0042] Figure 3 is a flowchart illustrating a message processing method provided in an embodiment of this application;

[0043] Figure 4a is a flowchart illustrating a message notification settings interface provided in an embodiment of this application;

[0044] Figure 4b is a flowchart illustrating another display message notification settings interface provided in an embodiment of this application;

[0045] Figure 4c is a flowchart illustrating another display message notification settings interface provided in an embodiment of this application;

[0046] Figure 5a is a schematic diagram of a process for setting a notification identifier according to an embodiment of this application;

[0047] Figure 5b is a flowchart illustrating the notification content for setting a notification method according to an embodiment of this application;

[0048] Figure 5c is a flowchart illustrating another notification method provided in an embodiment of this application.

[0049] Figure 6a is a flowchart illustrating another method for setting notifications provided in an embodiment of this application;

[0050] Figure 6b is a flowchart illustrating another method for setting notifications provided in an embodiment of this application;

[0051] Figure 7 is a schematic diagram of the update process of a notification method provided in an embodiment of this application;

[0052] Figure 8 is a schematic diagram of the interface for outputting the first notification message under different notification methods provided in an embodiment of this application;

[0053] Figure 9 is a flowchart of another message processing method provided in an embodiment of this application;

[0054] Figure 10 is a schematic diagram of a message notification management interface provided in an embodiment of this application;

[0055] Figure 11 is a diagram showing the relationship between a notification scenario, notification event, notification business module, and notification method provided in an embodiment of this application.

[0056] Figure 12 is a flowchart of another message processing method provided in an embodiment of this application;

[0057] Figure 13 is a schematic diagram of the structure of a domain model provided in an embodiment of this application;

[0058] Figure 14 is a flowchart of the aggregation design of a domain model provided in an embodiment of this application;

[0059] Figure 15 is a schematic diagram of a state machine provided in an embodiment of this application;

[0060] Figure 16 is a schematic diagram of the business architecture of a message processing method provided in an embodiment of this application;

[0061] Figure 17 is a schematic diagram of the application architecture of a notification center provided in an embodiment of this application;

[0062] Figure 18 is an interaction timing diagram of a notification method setting provided in an embodiment of this application;

[0063] Figure 19 is an interaction timing diagram of a message notification provided in an embodiment of this application;

[0064] Figure 20 is an interaction sequence diagram of a notification operation capability provided in an embodiment of this application;

[0065] Figure 21 is a schematic diagram of a message processing device provided in an embodiment of this application;

[0066] Figure 22 is a schematic diagram of another message processing device provided in an embodiment of this application;

[0067] Figure 23 is a schematic diagram of another message processing device provided in an embodiment of this application;

[0068] Figure 24 is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0069] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0070] The following is a description of the key terms used in this application.

[0071] (1) Notification method.

[0072] The notification method refers to the way a notification message is sent. In this application embodiment, the notification method refers to the method used when sending a notification message from the business system to a business object (e.g., a user in the business system). That is, the notification method instructs the business object in the business system on how to receive the sent notification message. For example, the notification methods involved in this application include, but are not limited to: SMS notification, email notification, social notification, in-site message notification, announcement notification, etc. SMS notification instructs the business object to receive the notification message via SMS; email notification instructs the business object to receive the notification message via email; social notification instructs the business object to receive the notification message via a social app; in-site message notification instructs the business object to receive the notification message through the message receiving module within the business system; and announcement notification instructs the business object to receive the notification message from the website or page where the announcement was published. In this application, business objects can customize at least one notification method, allowing them to receive notification messages through one or more customized notification methods.

[0073] (2) Notification method configuration information and configuration items.

[0074] Notification method configuration information refers to the configuration information for notification methods. The notification method configuration information involved in this application is used to indicate M1 notification methods, and therefore includes sub-configuration information for each of the M1 notification methods. Since a notification method is generated by setting a configuration item, the notification method configuration information refers to the information generated during the process of setting the configuration item. Specifically, the sub-configuration information for each notification method may include: a notification identifier and at least one message type, etc. The notification identifier refers to the identifier of the business object to which the notification message is output when the notification message is output according to the corresponding notification method (i.e., the business object being notified). For example: the notification identifier in the sub-configuration information of SMS notification can be a mobile phone identifier (a mobile phone identifier is an identifier used to uniquely identify a mobile phone device or user, such as a mobile phone number; in SMS notification, it is the notification identifier output as the notification message to the business object); the notification identifier in the sub-configuration information of email notification can be an email address identifier (an email address is an identifier used to uniquely identify an email account, such as an email address; in email notification, it is the notification identifier output as the notification message to the business object); the notification identifier in the sub-configuration information of social notification can be a social identifier (a social identifier is an identifier used to uniquely identify a user on a social platform, such as an account in a social application of a specific service provider; in social notification, it is the notification identifier output as the notification message to the business object); the notification identifier in the sub-configuration information of in-system message notification can be the identifier of the message receiving module within the business system (such as the in-system message receiving address); the notification identifier in the sub-configuration information of announcement notification can be the address of the website or page where the announcement is published, etc. Optionally, the sub-configuration information of any notification method in this application embodiment may include one or more notification identifiers, and these one or more notification identifiers may belong to the same business object or different business objects. For example, the sub-configuration information of the SMS notification method may include multiple mobile phone numbers of business object 1, that is, business object 1 can set any of its own mobile phone numbers as notification identifiers to receive SMS notifications through the set mobile phone numbers; in addition, the sub-configuration information of the SMS notification method may also include mobile phone number 1 of business object 1 and mobile phone number 2 of business object 2, that is, business object 1 can receive SMS notifications through its own mobile phone number 1, or it can receive SMS notifications through the mobile phone number 2 of business object 2 (such as its friends or relatives). The message type is used to indicate the type of notification message output in the notification scenario. For example, if the notification scenario is an asset transfer scenario, then according to the business functions of the business system involved in the notification scenario, the notification messages to be output in the notification scenario can be divided into four message types: first message type, second message type, third message type, and fourth message type.The first, second, third, and fourth message types are different types of notification messages that need to be output in a notification scenario, categorized according to the business functions of the business systems involved. For example, the first message type could be "Audit Notification," the second message type could be "Account Receipt Reminder," the third message type could be "Transaction Reminder," and the fourth message type could be "Benefits Information." It should be understood that the message types corresponding to the notification messages output in different notification scenarios may be the same or different.

[0075] A configuration item refers to a functional item used to set notification method configuration information. By performing setting operations on a configuration item, the notification method can be configured. For example, this application provides N configuration items, each used to set a specific notification method, with different configuration items setting different notification methods. For instance, the first configuration item (such as the "SMS notification" configuration item) is used to set the SMS notification method; the second configuration item (such as the "email notification" configuration item) is used to set the email notification method, and so on. Since the sub-configuration information for any notification method includes: a notification identifier and the message type of the notification message, and this sub-configuration information is generated during the process of setting the configuration item, a configuration item can include the following configuration fields: a notification identifier field and a notification content field; where the notification identifier field is used to set the notification identifier, and the notification content field is used to set the message type of the notification message. Therefore, by setting the configuration fields in a configuration item, the setting of a notification method can be completed.

[0076] (3) Business system.

[0077] A business system refers to a business platform that a service provider connects to or serves, and which provides business functions to business objects within a business scenario. This business system can be applied to any cross-regional business scenario, which refers to a business execution involving at least two different regions. Examples include cross-regional asset transfers, cross-regional e-commerce, and cross-regional logistics. The business functions provided by the business system may differ depending on the type of cross-regional business scenario. For instance, in a cross-regional asset transfer scenario, the business system provides asset transfer functionality; in a cross-regional e-commerce scenario, it provides e-commerce services; and in a cross-regional logistics scenario, it provides logistics services, and so on.

[0078] (4) Notification scenarios and notification messages.

[0079] Notification scenarios refer to business scenarios that require the output of notification messages. For illustrative purposes, the business scenarios in this application mainly involve cross-regional business scenarios. A cross-regional business scenario refers to a business execution involving at least two different regions; for example, cross-regional business scenarios can include, but are not limited to: cross-regional asset transfer scenarios (commonly known as money transfer scenarios), cross-regional e-commerce scenarios, cross-regional telecommunications scenarios, cross-regional logistics scenarios, cross-regional financial scenarios, and any other type of business scenario.

[0080] Notification messages refer to messages that a business system needs to output to business objects via notification. Notification messages can be output in various ways. For example, they can be sent to business objects via SMS (sending messages to them via text message); via email; or via social media applications. In other words, business objects can receive notification messages through multiple methods, thereby improving the effectiveness of notifications and ensuring that they receive them efficiently and promptly.

[0081] This application provides a message processing solution that supports business objects in customizing at least one notification method (such as SMS notification, email notification, social notification, etc.), which can meet the actual notification needs of business objects. Different business objects can personalize their notification methods according to their own needs, improving business convenience and flexibility. Notification messages in the business system can be output according to at least one notification method customized by the business object. This ensures that notification messages are processed according to the actual notification needs of the business object, guaranteeing convenient, efficient, and accurate output. The message processing solution of this application is applicable to various business scenarios that require the output of notification messages, including but not limited to: cross-regional asset transfer scenarios, cross-regional e-commerce scenarios, cross-regional logistics scenarios, etc.; this application does not limit the applicable scenarios.

[0082] It should be noted that the message processing solution provided in this application requires special explanation of the following two points:

[0083] 1. The relevant data involved in the message processing process in this application (such as notification method configuration information, notification messages, etc.). When the above embodiments of this application are applied to specific products or technologies, permission or consent from the target audience is required, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the region, conforming to the principles of legality, legitimacy, and necessity, and not involving the acquisition of data types prohibited or restricted by laws and regulations. In some optional embodiments, the relevant data involved in the embodiments of this application is obtained after separate authorization from the target audience. In addition, when obtaining separate authorization from the target audience, the purpose of the relevant data is explained to the target audience.

[0084] 2. It is understood that in this application, the term "at least one" refers to one or more, and "multiple" means two or more; for example, "at least one notification method" means one, two, or more notification methods. The terms "first," "second," etc., are used to distinguish identical or similar items with essentially the same function. It should be understood that there is no logical or temporal dependency between "first," "second," and "nth," nor is there any limitation on the quantity or execution order.

[0085] The message processing system provided in this application will be described in detail below with reference to Figures 1 and 2.

[0086] Please refer to Figure 1, which is a schematic diagram of the architecture of a message processing system provided in an embodiment of this application. As shown in Figure 1, the message processing system may include: multiple terminal devices (e.g., first terminal device 101, second terminal device 102, etc.) and a server 103. This application does not specifically limit the number of terminal devices and servers. For example, the first terminal device 101 may be a terminal device used by a first business object, the second terminal device 102 may be a terminal device used by a second business object, and the server 103 refers to the device corresponding to the notification center, and is used to provide background technical support for the first terminal device 101 and the second terminal device 102; wherein, the first business object may be any business object in the business system (such as any merchant involving cross-regional business), and the second business object may be a management object of the business system (such as an operations personnel). Each of the aforementioned terminal devices (such as the first terminal device 101 and the second terminal device 102) can be directly or indirectly connected to the server 103 via a network. The network may include, but is not limited to, wired networks and wireless networks. Wired networks may include local area networks (LANs), metropolitan area networks (MANs), and wide area networks (WANs). Wireless networks may include Bluetooth, Wi-Fi (Wireless Fidelity, a standard wireless LAN), and other networks that enable wireless communication. Furthermore, the first terminal device 101 can interact with other terminal devices (such as the second terminal device 102) connected to the server 103 via the server 103.

[0087] In the message processing system shown in Figure 1, any terminal device can include, but is not limited to: smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, in-vehicle terminals, smart wearable devices (such as smart bracelets, smart pedometers), virtual reality devices (such as VR (Virtual Reality) devices, AR (Augmented Reality) devices), smart robots, etc. Terminal devices are often equipped with display devices, which can be monitors, displays, touchscreens, etc., and touchscreens can be touchscreens, touch panels, etc. Furthermore, the server 103 in the message processing system shown in Figure 1 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0088] Please refer to Figure 2, which is a three-terminal interaction flowchart of a message processing method provided in an embodiment of this application. As shown in Figure 2, the three-terminal interaction flowchart mainly involves data interaction between a first terminal device, a second terminal device, and a server. The specific interaction flowchart is as follows:

[0089] 1. The first terminal device 101 (such as the terminal device used by the first business object (such as a merchant)) can display a message notification settings interface, which is used to set the notification method for the business system. The message notification settings interface contains N configuration items, each used to set a corresponding notification method for the business system, where N is a positive integer. For example, the first configuration item (such as the "SMS notification" configuration item) is used to set the SMS notification method; the second configuration item (such as the "email notification" configuration item) is used to set the email notification method; and the third configuration item (such as the "APP notification" configuration item) is used to set the social notification method. In specific applications, "APP" refers to the name of a specific social software.

[0090] 2. The first terminal device 101 receives the first setting operation; for example, the first setting operation here refers to the setting operation of the first business object on M1 of the N configuration items in the message notification interface.

[0091] 3. In response to the first setting operation, the first terminal device 101 sets notification method configuration information for the business system. This notification method configuration information indicates M1 notification methods, where M1 is a positive integer. Specifically, this application supports a business object (such as the first business object) to customize and select M1 configuration items from N configuration items, and to perform a setting operation on each of the selected M1 configuration items to obtain sub-configuration information for a notification method corresponding to that configuration item; then, the sub-configuration information of the M1 notification methods can be combined into notification method configuration information.

[0092] 4. The second terminal device 102 (such as the terminal device used by the second business object (such as the operator)) can display a message notification management interface. This message notification management interface is used by the second business object to perform notification management operations on the business system. The notification management operations include the second setting operations.

[0093] 5. The second terminal device 102 responds to the second setting operation by setting the notification message configuration information of the business system. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method. M2 is a positive integer.

[0094] 6. Server 103 obtains notification method configuration information from the first terminal device 101.

[0095] 7. Server 103 obtains notification message configuration information from the second terminal device 102.

[0096] 8. Server 103 encapsulates the first notification message in the business system based on the notification method configuration information and notification message configuration information.

[0097] 9. Send the encapsulated first notification message to the first terminal device 101.

[0098] 10. When the first terminal device 101 receives the first notification message from the business system, it outputs the first notification message in the M1 configured notification methods.

[0099] In one possible implementation, the message processing system provided in this application embodiment can be deployed in a blockchain network. For example, the first terminal device 101, the second terminal device 102, and the server 103 in the above system can all be regarded as node devices in the blockchain network, and these node devices together constitute the blockchain network. Therefore, the message processing process executed in this application embodiment can be executed on the blockchain, which can ensure the fairness and impartiality of the message processing process, make the process traceable, and ensure data security during message processing, thereby improving the security and reliability of the entire message processing process.

[0100] The message processing system provided in this application embodiment is used to execute the message processing scheme mentioned above. On the one hand, it supports business objects to customize at least one notification method (such as SMS notification, email notification, social notification, etc.) in the message notification interface, which can meet the actual notification needs of business objects. Moreover, different business objects can personalize the notification method according to their own needs, improving business convenience and flexibility. On the other hand, notification messages in the business system can be output according to various notification methods customized by business objects. This allows the notification messages of the business system to be processed according to the actual notification needs of business objects, ensuring that notification messages are output conveniently, efficiently, and accurately.

[0101] It is understood that the message processing system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new notification scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0102] The following is a detailed description of the product-side implementation of the message processing method of this application.

[0103] Please refer to Figure 3, which is a flowchart illustrating a message processing method provided in an embodiment of this application. This message processing method can be executed by a computer device, which can be the first terminal device shown in Figure 1, i.e., the terminal device where the first business object resides. As shown in Figure 3, the message processing method includes the following steps S301-S303:

[0104] S301. Display the message notification settings interface. The message notification settings interface is used to set the notification method for the business system.

[0105] The message notification settings interface is used to configure notification methods for business systems. For example, this interface may include N configuration items, each used to set a corresponding notification method for the business system, where N is a positive integer. In other words, the notification method for the business system can be configured using the N configuration items displayed in the message notification settings interface.

[0106] In one possible implementation, the method for triggering the display of the message notification settings interface can include any of the following (1)-(3):

[0107] (1) Display the service interface of the business system. This service interface has a message notification setting entry (e.g., message notification setting control, message notification setting function item, etc.). In response to the message notification setting entry being triggered, the message notification setting interface is displayed. Please refer to Figure 4a, which is a flowchart illustrating the display of a message notification setting interface provided in an embodiment of this application. As shown in Figure 4a, the service interface S401 of the business system can be displayed, and the service interface S401 displays at least one function item (e.g., "Message Notification Setting" function item, "Real-name Authentication" function item, "Activity Privilege" function item, etc.). Different function items are used to trigger the execution of different functions. For example, the "Message Notification Setting" function item is used to trigger the setting of notification methods. Business objects can click on the "Message Notification Setting" function item 4001, thereby triggering the display of the message notification setting interface S402.

[0108] (2) Display the service interface of the business system. The service interface has an operation area, which can be any area of ​​the service interface, such as the top area, center area, bottom area, etc. In response to a preset operation detected in the operation area, display the message notification setting interface. The preset operation includes any one of the following: gesture operation (e.g., drawing a symbol "S" or "V"), hover operation, single click operation, double click operation, and long press operation. Please refer to Figure 4b, which is a flowchart illustrating another display of the message notification setting interface provided in this application embodiment. As shown in Figure 4b, the service interface S401 of the business system can be displayed, and the service interface S401 has an operation area 4002. When a preset operation is detected in the operation area 4002 (e.g., drawing a symbol "V"), the message notification setting interface S402 is triggered to be displayed.

[0109] (3) Display the service interface of the business system. When the output of the setting prompt message is detected in the service interface and the setting prompt message is selected, the message notification setting interface is displayed. Please refer to Figure 4c, which is a flowchart illustrating another method for displaying the message notification setting interface provided in this embodiment of the application. As shown in Figure 4c, when a setting prompt message is received in the business system, such as a pop-up window, banner, or message, the business object can click on the setting prompt message (e.g., 4003 in service interface S401) to trigger the display of the message notification setting interface S402.

[0110] The message notification settings interface S402 displays N configuration items, such as those shown in Figure 4a: "APP Notification" configuration item 410, "SMS Notification" configuration item 420, and "Email Notification" configuration item 430. Each configuration item is used to configure a specific notification method; for example, "APP Notification" configuration item 410 is used to configure social notifications, "SMS Notification" configuration item 420 is used to configure SMS notifications, and "Email Notification" configuration item 430 is used to configure email notifications.

[0111] In one possible implementation, the message notification settings interface displays N configuration items. The following examples illustrate several different scenarios for determining these N configuration items:

[0112] 1) The message notification settings interface is displayed on the first terminal device, which refers to the terminal device used by the first business object in the business system. Based on the object type of the first business object, N configuration items matching the object type can be displayed. Each configuration item sets a notification method, where N is a positive integer and N≥M1. In this method, N configuration items are matched and displayed in the message notification settings interface based on the object type. Different object types may have different numbers and types of matching configuration items, thus achieving the effect of personalized display of different configuration items for different business objects, resulting in a personalized message notification settings interface.

[0113] Specifically, based on a preset object type-configuration item mapping table, and according to the object type of the first business object, N configuration items matching the object type of the first business object are searched from the mapping table. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1. Assuming the object type-configuration item mapping table is T, and the object type of the first business object is t, each row of the mapping table T is traversed. If the object type of a row is the same as t, the corresponding configuration item in that row is added to the set of matching configuration items. The final set is the N configuration items matching the object type of the first business object. The object type-configuration item mapping table T is a two-dimensional table.ij This represents the j-th configuration item corresponding to the i-th object type, where i represents the object type number and j represents the configuration item number.

[0114] The classification method for the object type of the first business object includes at least one of the following: ① Classification according to the geographical scope of the first business object. For example, if the first business object is located in the first region, then the first business object is of the first object type; if the first business object is located in the second region, then the first business object is of the second object type. The first region and the second region are different. ② Classification according to the permission level of the first business object in the business system. For example, the higher the permission level of the first business object, the larger the total number N of configuration items matching the first business object; conversely, the lower the permission level of the first business object, the smaller the total number N of configuration items matching the first business object. Optionally, the above permission level can be determined based on factors such as the activity level of the first business object in the business system (e.g., online time logged into the business system, frequency of operations performed using the business system to perform business processing, etc.) or the business transaction amount generated in the business system. For example, the permission level may include: Ordinary < VIP < SVIP, which can be classified according to the specific business scenarios applicable to the business system. ③ Divide according to the business scope of the first business object. For example, if the first business object is an electronic product merchant, then the business scope of the first business object is electronic products; if the first business object is a clothing merchant, then the business scope of the first business object is clothing; if the first business object is a food merchant, then the business scope of the first business object is food.

[0115] 2) Based on the system type of the business system, display N configuration items that match the system type. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1. In this mode, the corresponding N configuration items are matched and displayed in the message notification settings interface based on the system type. That is, these N configuration items are the configuration items supported by the current business system.

[0116] Specifically, based on a pre-defined system type-configuration item mapping table, N configuration items matching the system type of the business system are searched from the table. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1. Assuming the system type-configuration item mapping table is S, and the system type of the business system is s, each row of the mapping table S is traversed. If the system type of a row is the same as s, the corresponding configuration item in that row is added to the set of matching configuration items. The final set is the N configuration items matching the system type of the business system. The system type-configuration item mapping table S is a two-dimensional table. ijThis represents the j-th configuration item corresponding to the i-th system type, where i represents the system type number and j represents the configuration item number.

[0117] The classification methods for business system types include at least one of the following: ① Classification by business function, for example, the business functions supported by the business system include: B2C (Business to Customer) asset transfer business and B2B (Business to Business) asset transfer business. ② Classification by business scope, for example, the business scope supported by the business system may include, but is not limited to: electronic products, clothing, food, cosmetics, etc. ③ Classification by geographical scope involved in the business functions of the business system, that is, the configuration items matched in different geographical areas may be different, and different notification methods can be triggered in different geographical areas.

[0118] Based on this, the N configuration items mentioned above can be determined based on the object type of the business object or the system type of the business system, thus providing personalized display configuration items for business objects (such as business objects) and meeting the flexibility requirements of different business objects in setting notification methods.

[0119] S302. In response to the first setting operation, set the notification method configuration information for the business system. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer.

[0120] In response to the conditions or states on which the operation performed (e.g., the first setting operation on the first configuration item) depends, one or more operations performed may be performed in real time or with a set delay when the conditions or states on which they depend are met; unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0121] Any one of the N configuration items is designated as the first configuration item. The first setting operation includes triggering the first configuration item among the N configuration items, and the first configuration item is used to set the first notification method. The notification method configuration information indicates M1 notification methods (M1≤N), meaning that the business object (such as the first business object) selects M1 configuration items from the N configuration items for setting, thereby setting M1 notification methods for the business system. Therefore, the notification method configuration information includes sub-configuration information for the M1 notification methods.

[0122] In one possible implementation, the notification method configuration information includes the sub-configuration information of the first notification method. The process of generating the sub-configuration information of any notification method (such as the first notification method) is as follows: (1) Respond to the trigger operation of the first configuration item and receive the parameter information of the configuration field in the first configuration item. The configuration field of the first configuration item includes the first notification identifier field and the first notification content field. The first notification identifier field is used to set the destination identifier to which the notification message is output when the notification message is output according to the first notification method. The first notification content field is used to set the message type of the notification message output according to the first notification method. (2) Generate the sub-configuration information of the first notification method according to the parameter information of the configuration field in the first configuration item. It can be seen that the essence of the setting process for any notification method is the parameter configuration process of the configuration field of the corresponding setting item, so as to obtain the sub-configuration information corresponding to the notification method based on the configured parameter information. That is, the sub-configuration information includes: notification identifier and message type. The notification identifiers here can include: mobile phone identifiers (such as mobile phone numbers), email identifiers (such as email addresses), social identifiers, communication identifiers within the business system (such as internal messages), etc., and one type of notification identifier corresponds to one type of notification identifier. For example, the notification identifier for SMS notifications is a mobile phone identifier (such as mobile phone numbers), the notification identifier for email notifications is an email identifier (such as email address), and the notification identifier for social notifications is a social identifier.

[0123] The following instructions, with reference to the accompanying diagrams, explain the setup process for any notification method (such as SMS notification):

[0124] Please refer to Figure 5a, which is a flowchart illustrating the process of setting a notification identifier for a notification method according to an embodiment of this application. As shown in Figure 5a, the message notification interface displays N configuration items, which may specifically include three configuration items: "APP Notification" configuration item 501, "SMS Notification" configuration item 502, and "Email Notification" configuration item 503. Each configuration item includes a configuration field, which is used to configure the sub-configuration information of the corresponding notification method. Assuming the first configuration item is the "SMS Notification" configuration item, the configuration fields of the "SMS Notification" configuration item include: a first notification identifier field 5021 and a first notification content field 5022. The first notification identifier field 5021 is used to configure the notification identifier of the SMS notification method, and the first notification content field 5022 is used to configure the notification content of the SMS notification method (i.e., the message type of the notification message). A business object (such as the first business object) can click the first notification identifier field 5021 of the "SMS Notification" configuration item to trigger the display of the mobile phone binding interface. The business object can enter the first notification identifier (such as a mobile phone number) in this interface and then click the confirmation control 5002 to complete the setting of the notification identifier in the first notification identifier field. Furthermore, after completing the setting of the first notification identifier field, a prompt message (such as "Mobile phone binding successful") can be output in the message notification settings interface, and the set notification identifier can be displayed in the first notification identifier field (such as 5003) of the "SMS Notification" configuration item. It should be noted that when setting the notification identifier, the business object (such as the first business object) can set its own mobile phone number, or it can set a mobile phone number other than its own; there is no specific limitation on this. Optionally, this application also supports setting multiple notification identifiers in the first notification identifier field.

[0125] Further, please refer to Figure 5b, which is a flowchart illustrating the process of setting notification content for a notification method according to an embodiment of this application. As shown in Figure 5b, assuming the first configuration item is the "SMS Notification" configuration item, a business object (such as a first business object) can click the first notification content field of the "SMS Notification" configuration item to trigger the display of the notification content interface. This notification content interface displays at least one message type of notification messages from the business system. For example, the message types corresponding to the business system include: audit notification, payment reminder, transaction reminder, and welfare information. The system allows business objects to select one or more message types as needed in the notification content interface, and uses the selected message type as the message type corresponding to the first notification method (i.e., SMS notification method) of the first configuration item. For example, if the business object selects all message types in the notification content interface, clicking the confirmation control 5004 in the notification content interface completes the setting of the first notification content field. Furthermore, after the business object completes the setting of the first notification content field of the first configuration item, the set first configuration item 5005 can be displayed in the message notification settings interface. The first notification identifier field of the set first configuration item 5005 includes a notification identifier (such as a mobile phone number), and the first notification content field includes at least one message type (such as: audit notification, payment reminder, transaction reminder, welfare information). Based on this, the setting process of the first configuration item can be completed through the process shown in Figures 5a and 5b, thereby setting the first notification method.

[0126] Optionally, priority settings can be configured for notification content under any notification method. Please refer to Figure 5c, which is a flowchart illustrating another method for setting notification content according to an embodiment of this application. As shown in Figure 5c, the SMS notification content interface displays notification content of at least one message type, such as: review notification, payment reminder, transaction reminder, and welfare information. The message types under these options are displayed in order, and the earlier a message type appears in the SMS notification content interface, the higher its priority. This priority indicates the sending order of notification messages under the corresponding message type. For example, the priority of the "review notification" option is higher than that of the "payment reminder," so notification messages of the "review notification" type are sent before notification messages of the "payment reminder" type. In this system, business users can select any message type option (e.g., select "Transaction Alerts") and drag the "Transaction Alerts" option to rearrange them. For example, dragging the "Transaction Alerts" option to the top will display the reordered notification content in the message notification interface. It's clear that the "Transaction Alerts" option, dragged to the top, is at the top of the list, meaning notifications under this "Transaction Alerts" type have the highest priority. Similarly, notifications under the "Audit Notification" type have the second highest priority, and notifications under the "Benefits Information" type have the lowest priority. Based on this, business users can set the sending order of notifications under different message types by dragging and sorting them, thus meeting the personalized needs of different business users for sending different types of notifications.

[0127] Similarly, based on the SMS notification setup process shown in Figures 5a-5c, this application embodiment can further set an email notification method. Please refer to Figure 6a, which is a flowchart illustrating another notification setting method provided by this application embodiment. As shown in Figure 6a, the message notification interface displays N configuration items, which specifically include three configuration items: "APP Notification," "SMS Notification," and "Email Notification." Assuming the first configuration item is the "Email Notification" configuration item, which is used to set the email notification method, and includes a notification identifier field 601 and a notification content field 602, the process of setting the email notification method is as follows: In response to the business object's trigger operation on the notification identifier field 601, an email binding interface is displayed. The business object can enter the email identifier (e.g., email: 111111@xx.com) in this interface, and after successful verification of the email address, click the "OK" control in the email binding interface to complete the setting of the notification identifier (e.g., email address) in the notification identifier field under the email notification method. Furthermore, after completing the setting of the notification identifier field, a prompt message (e.g., email binding successful) can be output in the message notification settings interface, and the set notification identifier (e.g., email address) will be displayed in the notification identifier field of the "Email Notification" configuration item. It should be noted that the setting process for the notification content field 602 under the email notification method can be referred to the setting process shown in Figure 5b above, and will not be repeated here.

[0128] Similarly, based on the SMS notification setting process shown in Figures 5a-5c, this application embodiment can further set a social notification method. Please refer to Figure 6b, which is a flowchart illustrating another notification setting method provided by this application embodiment. As shown in Figure 6b, the message notification interface displays N configuration items, which specifically include three configuration items: "APP Notification," "SMS Notification," and "Email Notification." Assuming the first configuration item is the "APP Notification" configuration item, which is used to set the social notification method, and that the "APP Notification" configuration item includes a notification identifier field 603 and a notification content field 604, the social notification setting process is as follows: In response to the business object's trigger operation on the notification identifier field 603, a social binding interface is displayed, which displays a QR code 605 for triggering the binding of a notification identifier (such as a social identifier); in response to the scanning operation of the QR code 605, a message interface of the social platform (the identifier of the business object in the social platform is the social identifier) ​​is displayed. The social platform message interface displays a prompt message 606 sent by the social platform for binding a social identifier. The business object triggers (e.g., clicks) this prompt message 606, thereby triggering an interface that displays the binding of the business object's social identifier with the social notification method (this interface includes a confirmation binding control 607). After responding to the trigger operation on the confirmation binding control 607 in this interface, the setting of the notification identifier in the notification identifier field under the social notification method can be completed. Furthermore, the setting process for the notification content field 604 under the social notification method can be referred to the setting process shown in Figure 5b above, and will not be repeated here.

[0129] In summary, this application embodiment allows for the setting of N notification methods for a business system through N configuration items in the message notification interface, with each configuration item used to set one notification method. Based on this, a business object (such as a first business object) can customize at least one notification method (such as M1 notification methods) for the business system, thereby improving the convenience and flexibility of setting notification methods.

[0130] In one possible implementation, any of the M1 notification methods configured above can be updated. In response to a notification method change event, the notification method configuration information is updated; the notification method change event includes at least one of the following: (1) The first business object in the business system performs an editing operation on the sub-configuration information of any of the M1 notification methods. For example, the business object (such as the first business object) performs one or more of the following operations: modification, deletion, or addition of the notification identifier or notification content under any notification method. (2) The object type of the first business object changes. For example, the first business object changes from a regular object in the business system to a VIP object, or from an electronic product type object to a clothing type object. (3) The system type of the business system changes. For example, the business function of the business system changes from B2C asset transfer business to B2B asset transfer business, or the geographical scope involved in the business system changes from a first geographical scope to a second geographical scope. Among them, the above-mentioned business systems are applied in cross-regional business scenarios, which refer to business execution involving at least two different regions. For example, the business systems are applied to cross-regional asset transfer scenarios, cross-regional e-commerce scenarios, cross-regional logistics scenarios, cross-regional telecommunications scenarios, etc.

[0131] Please refer to Figure 7, which is a schematic diagram of the update process of a notification method provided in an embodiment of this application. As shown in Figure 7, the message notification settings interface displays at least one configured notification method (e.g., social notification method, SMS notification method, email notification method); in addition, each notification method displays corresponding sub-configuration information (such as notification identifier and message type), and supports modification of the sub-configuration information of each notification method. For example, each notification method displayed in the message notification settings interface (such as SMS notification method) is correspondingly set with an identifier editing control 801 and a type editing control 802, wherein the identifier editing control 801 is used to edit the notification identifier under the SMS notification method, and the type editing control 802 is used to edit the message type under the SMS notification method. If a business object performs a trigger operation on the identifier editing control 801, a notification method change event is generated, which in turn triggers an output editing pop-up. This pop-up supports editing operations (such as modification, addition, and deletion) on the notification identifier (e.g., mobile phone number) under the SMS notification method. Optionally, during the editing process of the notification identifier (e.g., mobile phone number), it supports changing the current business object's mobile phone number to that of another business object, or adding multiple mobile phone numbers of other business objects (the above process requires risk control verification to improve the security of the notification method update process). For example, after modifying the notification identifier (e.g., mobile phone number) to obtain the modified mobile phone number (as shown in 803), upon detecting a trigger operation on the confirmation change control 804 in the editing pop-up, the notification identifier under the SMS notification method can be updated, thereby updating the notification method configuration information. Similarly, the change process for the sub-configuration information of other notification methods can also refer to the change process shown in Figure 7, which will not be elaborated here.

[0132] S303. When the first notification message is received from the business system, the first notification message is output in the M1 notification methods set.

[0133] A business system generates a large number of business messages, and these messages, which need to be sent to business objects, are also called notification messages. Here, the first notification message refers to any single notification message. Since step S302 allows business objects to customize at least one notification method (e.g., M1 notification methods), upon receiving the first notification message, the pre-defined M1 notification methods can be used to output the first notification message. For example, suppose the pre-defined M1 notification methods include: SMS notification, email notification, and social media notification. The following, with reference to the accompanying diagram, illustrates the specific process of outputting the first notification message under different notification methods.

[0134] Please refer to Figure 8, which is a schematic diagram of the interface for outputting the first notification message under different notification methods provided in an embodiment of this application. As shown in Figure 8(a), this figure is a schematic diagram of the interface for outputting the first notification message under SMS notification method; as shown in Figure 8(b), this figure is a schematic diagram of the interface for outputting the first notification message under social notification method; as shown in Figure 8(c), this figure is a schematic diagram of the interface for outputting the first notification message under email notification method. It can be seen that, for the same notification message (such as the first notification message) generated by a business object in the same business system, this application supports outputting the first notification message using different notification methods, and the message format and message content of the first notification message output under different notification methods may be different. For example, the format and message content of the first notification message output under SMS notification method are different from those under social notification method. Based on this, the embodiment of this application supports outputting the first notification message using the set M1 notification methods. Even if a certain notification method is unavailable or has a fault, the business object can still receive the notification message in a timely manner through other notification methods, which can avoid missing important information due to the failure of a single notification method. This approach of outputting notification messages based on multiple notification methods can improve the reliability of message delivery, thereby increasing the attention and processing efficiency of business objects to notification messages.

[0135] This application provides a message processing solution that supports business objects (such as any business object) in customizing at least one notification method. On one hand, business objects can visually set the notification method of the business system through a message notification settings interface, improving the flexibility of notification method settings and business interactivity. On the other hand, this application also supports customizing at least one notification method (such as SMS, email, social APP, etc.) for business objects, meeting their actual notification needs. Different business objects can personalize their notification methods according to their own needs, improving business convenience and flexibility. Furthermore, notification messages in the business system can be output according to at least one notification method customized by the business object. This ensures that notification messages are processed according to the actual notification needs of the business object, guaranteeing convenient, efficient, and accurate output. Consequently, business objects can receive and process notification messages in the business system in a timely manner, improving business processing efficiency.

[0136] The following is a detailed description of the operation and management side implementation of the message processing method of this application.

[0137] Please refer to Figure 9, which is a flowchart of another message processing method provided in an embodiment of this application. This message processing method can be executed by a computer device, which can be the second terminal device shown in Figure 1, i.e., the terminal device where the second business object (such as an operator) is located. As shown in Figure 9, the message processing method includes the following steps S901-S903:

[0138] S901, Display message notification management interface.

[0139] The message notification management interface is used to perform notification management operations on the business system. Specifically, the notification management operation instructs the management of the business system, which includes at least one of the following: managing the notification methods of the business system, managing the notification messages to be sent by the business system, and managing the notification scenarios applicable to the business system. For example, the notification management operation here includes a second setting operation, which is used to trigger the setting of notification message configuration information for the business system.

[0140] Please refer to Figure 10, which is a schematic diagram of a message notification management interface provided in an embodiment of this application. As shown in Figure 10, the message notification management interface includes at least one management item. Different management items are used to configure a type of configuration information for the business system. For example, the management items here may include: notification scenario management item 1001, notification method management item 1002, notification template management item 1003, etc. Different management items are used to manage different information. For example, notification scenario management item 1001 is used to manage the notification scenarios applicable to the business system, notification method management item 1002 is used to manage the notification methods set by the business object for the business system, and notification template management item 1003 is used to manage the notification templates of the notification messages to be sent in the business system.

[0141] S902. In response to the second setting operation, set the notification message configuration information of the business system; the notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system; the notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer.

[0142] Specifically, the second setting operation may include: a trigger operation performed by the second business object on the notification scenario management item, and a trigger operation performed on the notification template management item. Specifically, in response to the trigger operation performed on the notification scenario management item, the notification scenario configuration information of the business system is set; and in response to the trigger operation performed on the notification template management item, the notification template configuration information of the business system is set.

[0143] (1) The notification scenario configuration information includes at least one of the following: the description information of the notification scenario, the description information of the notification event in the notification scenario, the identifier of the business function module corresponding to the notification event, the object type of the business object being notified, the identifier of the M2 notification methods configured for the notification event, the number of retries when the notification message is sent, and the retry time when the notification message is sent.

[0144] (2) The notification template configuration information includes at least one of the following: a description of the applicable notification scenario, a description of the applicable notification event, an identifier of the applicable business function module, an identifier of the applicable notification method, and a description of the notification template; the description of the notification template includes the identifier of the notification template, the message format of the notification template, and the validity period of use. For example, the specific information included in the above notification template configuration information can be shown in Table 1 below:

[0145] Table 1. Information Content of Notification Template Configuration Information

[0146] Based on this, the embodiments of this application can provide message notification management capabilities for second business entities (such as operators of business systems), and manage information such as notification scenarios, notification business modules, notification events, and notification methods through the configured notification template information. Based on the notification template configuration information, the second business entity can flexibly define and manage different notification messages, and configure the format and method of the notification messages according to specific business needs. At the same time, the validity period of the notification template allows the second business entity to update and adjust the notification template in a timely manner to flexibly adapt to different business needs and changes.

[0147] In one possible implementation, in a cross-regional business scenario, the business system can generate a large number of notification messages that need to be sent to business objects. This embodiment classifies the notification messages sent to each business object according to the business function modules of the business system. The message types of the notification messages can include: audit notifications, payment reminders, transaction reminders, welfare information, etc. The relationship between notification scenarios, notification events, notification methods, and notification business modules is explained below with reference to the accompanying drawings. Please refer to Figure 11, which is a diagram illustrating the relationship between a notification scenario, notification event, notification business module, and notification method provided in this embodiment. As shown in Figure 11, a notification scenario includes at least one notification event. Each notification event belongs to a business function module in the business system. Whenever any business function module in the business system is triggered to generate a corresponding notification event, a notification message needs to be sent to the business objects in the business system. The notification message corresponding to each notification event supports output using at least one notification method (e.g., SMS notification, email notification, social notification, etc.).

[0148] In one possible implementation, the aforementioned management operations further include batch notification operations, which provide the function of sending notification messages in batches. Specifically, in response to the batch notification operation, a message file is received. This message file contains the message content of the target messages to be batch-notified and batch notification description information. The batch notification description information includes at least one of the following: the type of business object to be batch-notified, the identifier of the notification method used for the batch notification, and the description information of the notification template corresponding to the notification method used for the batch notification. The batch notification operation occurs when an anomaly is detected in the business system (such as a network outage) and a resend notification message is required, or when the running time of the business system is detected to be within a preset time period (such as a holiday). Further, the target messages can be batch-notified according to the message file. Batch notification refers to performing a single sending operation on multiple notification messages, i.e., a single sending operation is used to send multiple notification messages. Based on this, the batch sending notification message processing flow can provide more efficient notification management capabilities for the second business object, thereby improving the convenience and efficiency of the notification management process.

[0149] S903. Send notification messages to business objects in the business system according to the notification message configuration information of the business system.

[0150] Specifically, since the notification message configuration information of the business system includes notification scenario configuration information and notification template configuration information, in the process of sending notification messages to business objects in the business system: based on the notification scenario configuration information, it is possible to determine in which notification scenarios notification messages need to be sent to business objects in the business system; and based on the notification template configuration information, it is possible to determine the notification template (such as message format, validity period, etc.) corresponding to the notification message sent to the business object.

[0151] In this embodiment, a message notification management interface can be displayed, providing a second business entity (such as operations personnel) with notification operation capabilities for the business system. This notification operation capability provides operations personnel with a centralized platform for managing and operating notification messages, enabling them to better configure, manage, and query the sending status of notification messages. Operation personnel can conveniently configure notification scenario configuration information, notification template configuration information, and other notification message configuration information within the message notification interface. This method of managing notification operations for the business system through an intuitive visual interface (message notification management interface) improves the efficiency and convenience of notification operation management.

[0152] The following is a detailed description of the backend technology implementation corresponding to the message processing method of this application.

[0153] Please refer to Figure 12, which is a flowchart of another message processing method provided in an embodiment of this application. This message processing method can be performed by a computer device, which can be a server (e.g., a notification center) as shown in Figure 1. As shown in Figure 12, the message processing method includes the following steps S1201-S1204:

[0154] S1201. Obtain notification method configuration information for the business system from the first terminal device.

[0155] Specifically, the notification method configuration information is used to indicate M1 notification methods (e.g., SMS notification, email notification, social notification, etc.), where M1 is a positive integer. For example, the notification method configuration information includes sub-configuration information for each of the M1 notification methods, and the sub-configuration information for any one notification method includes: notification identifier and message type. It should be noted that the detailed process of setting the notification method configuration information can be referred to the flow shown in step S302 of the embodiment in Figure 3, and will not be repeated here.

[0156] S1202. Obtain the notification message configuration information of the business system from the second terminal device.

[0157] Specifically, the notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system; the notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer; M1 and M2 may be the same or different. The notification scenario configuration information includes at least one of the following: a description of the notification scenario, a description of the notification event in the notification scenario, an identifier of the business function module corresponding to the notification event, the object type of the notified business object, the identifier of the M2 notification methods configured for the notification event, the number of retries when the notification message is sent, and the retry time when the notification message is sent. The notification template configuration information includes at least one of the following: a description of the applicable notification scenario, a description of the applicable notification event, an identifier of the applicable business function module, an identifier of the applicable notification method, and a description of the notification template. The description of the notification template includes the identifier of the notification template, the message format of the notification template, and its validity period. It should be noted that the process of setting the notification message configuration information can refer to the flow shown in step S902 of the embodiment in Figure 9, and will not be repeated here in this embodiment.

[0158] S1203. Based on the notification method configuration information and notification message configuration information, encapsulate and process the first notification message in the business system.

[0159] In one possible implementation, the first notification message refers to any notification message in the business system. Specifically, the process of encapsulating the first notification message in the business system based on the notification method configuration information and the notification message configuration information includes the following steps (1)-(2):

[0160] (1) Based on the notification method configuration information and the notification message configuration information, determine the M3 notification methods to be used for the first notification message. The notification method configuration information indicates the M1 notification methods set by the first business object, and the notification message configuration information indicates the M2 notification methods configured by the second business object. Therefore, the M3 notification methods refer to the intersection of the M1 and M2 notification methods, where M3 is a positive integer. For example, the M1 notification methods include: SMS notification, email notification, and social notification; the M2 notification methods include: SMS notification and email notification; therefore, the M3 notification methods include: SMS notification and email notification.

[0161] Let set A represent the M1 notification methods indicated by the notification method configuration information, and set B represent the M2 notification methods indicated by the notification message configuration information. Initialize an empty set C as the intersection set. Iterate through each element 'a' in set A, checking if element 'a' exists in set B. If it does, add element 'a' to set C. Set C represents the M3 notification methods to be used for the first notification message, where M3 is a positive integer.

[0162] (2) Encapsulate the first notification message according to the notification templates corresponding to the M3 notification methods. As shown in Table 1 above, since different notification methods correspond to different notification templates, and the description information (including message format and validity period) of different notification templates are different, it is necessary to encapsulate the first notification message according to the notification template corresponding to each notification method to obtain a first notification message corresponding to that notification method. For example, the M3 notification methods include: SMS notification, email notification, and social notification. The message result after encapsulating the first notification message using the notification template for SMS notification can be shown in Figure 8(a), the message result after encapsulating the first notification message using the notification template for social notification can be shown in Figure 8(b), and the message result after encapsulating the first notification message using the notification template for email notification can be shown in Figure 8(c).

[0163] Based on this, when encapsulating any notification message in the business system, the M3 notification methods allowed for the notification message can be determined by finding the intersection between the M1 notification methods configured by the business object (such as the first business object) and the M2 notification methods configured by the operations personnel (such as the second business object). Then, different notification templates corresponding to different notification methods are used to encapsulate the notification message respectively.

[0164] In one possible implementation, a domain model is obtained, and the complete business process of the business system (such as the notification message sending process, the configuration process of operation personnel, and the process of setting notification methods for business objects) is comprehensively managed through the domain model. Here, the domain model refers to an architecture used to manage the business processes of a corresponding domain. Please refer to Figure 13, which is a schematic diagram of the structure of a domain model provided in an embodiment of this application. As shown in Figure 13, the domain model includes: a notification management model, a notification template information model, and a notification method information model; wherein, the notification method information model can be called to manage the notification method configuration information, the notification template information model can be called to manage the notification message configuration information (including notification template configuration information and notification scenario configuration information), and the notification management model can be called to manage the sending process of the first notification message in the business system. Further, please refer to Figure 14, which is a flowchart of the aggregation design of a domain model provided in an embodiment of this application. As shown in Figure 14, the management architecture of the various domain models (notification management model, notification template information model, and notification method information model) is constructed using an aggregation design approach. Each domain model has its own aggregation root identifier, and each domain model interacts with other domain models through the aggregation root identifier during its respective management process. Aggregation design is a software design method commonly used in Domain-Driven Design (DDD). It focuses on simplifying complex domain models into a set of aggregations, where each aggregation represents a dataset and related business logic within a consistency boundary.

[0165] Based on this, domain models are designed to comprehensively manage the complete business processes of the business system. Since different domain models are responsible for managing different business processes (e.g., the notification method information model manages the notification method configuration information on the business object side, the notification target information model manages the notification message configuration information on the operations personnel side, and the notification management model manages the notification message sending process in the business system), it can ensure that each domain model performs its own function and maintains independence. In addition, the management architecture is constructed using an aggregation design approach, which can link and collaborate between the various domain models, thereby ensuring the integrity and consistency between the various domain models.

[0166] S1204. The encapsulated first notification message is sent to the first terminal device for output.

[0167] In one possible implementation, after encapsulation, M3 first notification messages are obtained, and each of the M3 first notification messages corresponds one-to-one with one of the M3 notification methods. Specifically, the process of sending the encapsulated notification messages to the first terminal device for output includes the following steps (1)-(2):

[0168] (1) Prepare for the sending of M3 first notification messages in the first transaction procedure. Here, the first transaction procedure refers to the program running local transactions. A local transaction is a set of operations (such as the sending operation mentioned above) executed within a single database or resource manager. These operations either all commit successfully or all roll back, ensuring the consistency and integrity of the data (such as M3 first notification messages). Local transactions typically have the following characteristics (ACID properties):

[0169] 1. Atomicity: All operations in a transaction either complete completely or fail to complete completely; there is no case where only some operations are completed.

[0170] 2. Consistency: The database state must remain consistent before and after a transaction is executed.

[0171] 3. Isolation: When multiple transactions are executed concurrently, the operations of one transaction will not affect other transactions.

[0172] 4. Durability: Once a transaction is committed, its results will be permanently stored in the database and will not be lost even if the system fails.

[0173] (2) An idempotent control strategy is used to control the sending operation in the first transaction procedure so that one of the M3 first notification messages is sent to the first terminal device for output.

[0174] The so-called idempotency control strategy aims to ensure that the business system produces the same result when making repeated requests or operations, avoiding data inconsistencies or errors caused by repeated operations. Specifically, if the result of multiple executions of an operation is the same as the result of a single execution, then the operation is idempotent. For example, this application has M3 notification methods, and each notification method is used to notify a corresponding first notification message. Therefore, for M3 first notification messages, M3 sending operations are required. Since the result of these M3 sending operations is the same as the result of a single sending operation, the sending operations for these M3 first notification messages in this application are idempotent. Thus, by employing the aforementioned idempotency control strategy, it can be ensured that only one first notification message needs to be sent to the first terminal device, thereby preventing the business object from repeatedly receiving multiple identical notification messages.

[0175] The specific implementation principle of the idempotent control strategy is as follows: A unique index is created in the database of the notification center. The fields of this index are the request serial number ID (business order number, such as withdrawal order number) generated by the business system and the notification scenario. Before executing the sending operation, it is first checked whether the record of the current request already exists in the unique index. If it exists and the parameters of the two requests are consistent, the sending operation is not executed; if it does not exist, the sending operation is executed and the request record is inserted into the unique index, thereby ensuring that only one first notification message needs to be sent to the first terminal device, so as to avoid the business object receiving multiple identical notification messages.

[0176] In a specific application example, an idempotent control strategy is used to control the sending operation in the first transaction procedure. Specifically, a unique index is created in the notification center's database. The fields of this index are the request serial number ID (business order number, such as a withdrawal order number) generated by the business system and the notification scenario. Before executing the sending operation, it checks whether a record for the current request already exists in this unique index. If it exists and the parameters of the two requests are consistent, the sending operation is not performed; otherwise, the sending operation is performed, and the request record is inserted into the unique index, so that one of the M3 first notification messages is sent to the first terminal device for output.

[0177] Based on this, during the sending of any notification message (such as the first notification message), local transactions and idempotent control strategies can be used to control the sending process of the notification message. On the one hand, local transactions can ensure that the sending operation of the notification message satisfies the ACID properties; on the other hand, idempotent control strategies can ensure that multiple identical first notification messages will not be sent to the business object repeatedly, thus avoiding sending duplicate notification messages and interfering with the business object.

[0178] In one possible implementation, the business system also includes a second notification message. Similarly, since there are M3 notification methods, the second notification message is encapsulated to obtain M3 second notification messages, each corresponding one-to-one with one of the M3 notification methods. Specifically, the sending operation of the M3 second notification messages can be prepared in a second transaction program, which is a different transaction program from the first transaction program; for example, the first transaction program is the first program running a local transaction, and the second transaction program is the second program running a local transaction. The first program and the second program are different; that is, the first transaction program and the second transaction program are different programs running local transactions. Further, a concurrency control strategy is adopted to send the first notification message and the second notification message concurrently to the first terminal device for output. The concurrency control strategy refers to an access strategy used to manage the business system in a multi-business object or multi-task environment (such as a task sending the first notification message and a task sending the second notification message) to ensure that data consistency and integrity are not compromised when multiple operations are performed simultaneously. The concurrency control strategy mainly involves the following mechanisms:

[0179] 1. Locking mechanism:

[0180] Shared locks (read locks): Allow multiple transactions to read the same data simultaneously, but prevent write operations. Also known as read locks, shared locks are a type of locking mechanism in concurrency control strategies. They allow multiple transactions to read the same data concurrently, but prevent write operations, ensuring that data consistency and integrity are not compromised when multiple transactions read data simultaneously.

[0181] Exclusive lock (write lock): Prevents other transactions from reading or writing data until the lock is released. Also known as a write lock, it's a concurrency control mechanism that prevents other transactions from reading or writing data until the lock is released, ensuring data consistency and integrity by preventing interference from other transactions during write operations.

[0182] 2. Multi-Version Concurrency Control (MVCC):

[0183] By saving historical versions of data, read operations are allowed to be unblocked by write operations.

[0184] 3. Timestamp sorting:

[0185] Each transaction is assigned a unique timestamp, and operations are executed in chronological order to ensure sequential execution. Timestamp sorting is a mechanism in concurrency control strategies; assigning a unique timestamp to each transaction and executing operations in chronological order ensures sequential execution and avoids data conflicts and inconsistencies caused by concurrent operations.

[0186] 4. Optimistic concurrency control:

[0187] Assuming few conflicts, optimistic concurrency control is a mechanism among concurrency control strategies. It assumes few conflicts, does not acquire locks during transaction execution, checks for conflicts upon commit, and rolls back if conflicts are found. This mechanism can improve system concurrency performance and reduce the use of locks.

[0188] 5. Pessimistic concurrency control:

[0189] Assuming high conflict rates, pessimistic concurrency control employs locking during transaction execution to prevent other transactions from accessing the data. This mechanism ensures data consistency and integrity, but may reduce system concurrency performance.

[0190] A concurrency control strategy is adopted to concurrently send the first and second notification messages to the first terminal device for output. The specific application is as follows: When the task of sending the first and second notification messages starts, processing is performed according to different mechanisms of the concurrency control strategy. If a locking mechanism is used, for a shared lock (read lock), multiple transaction programs are allowed to read the relevant data of the notification message simultaneously, but write operations are blocked; for an exclusive lock (write lock), when a notification message is sent, other transaction programs are prevented from reading or writing the data of that notification message until the lock is released. If Multi-Version Concurrency Control (MVCC) is used, by saving historical versions of the notification message data, read operations are allowed without being blocked by write operations. If timestamp sorting is used, a unique timestamp is assigned to each transaction program sending a notification message, and operations are executed in chronological order to ensure sequential execution of transaction programs. If optimistic concurrency control is used, assuming few conflicts, no locks are acquired during transaction execution; conflicts are checked during commit, and if conflicts are found, a rollback is performed. If pessimistic concurrency control is used, assuming many conflicts, locks are acquired during transaction execution to prevent other transactions from accessing the notification message data.

[0191] Based on this, a concurrency control strategy is adopted to output multiple notification messages (such as the first notification message and the second notification message) in the business system concurrently. Through mechanisms such as locking, MVCC, timestamp sorting, optimistic control and pessimistic control, the consistency and integrity of data (such as the first notification message and the second notification message) in a multi-business object or multi-task environment are ensured, and the sending efficiency of notification messages can be improved.

[0192] In one possible implementation, the sending state of the first notification message can be described by a state machine. Specifically, the state machine generated during the sending of the first notification message is obtained; wherein, the state machine is used to describe the different states corresponding to the first notification message during the sending process, for example, the states described by the state machine include: start state, processing state, sending success state, sending failure state, sending retry state, and retry limit failure state. Please refer to Figure 15, which is a schematic diagram of the structure of a state machine provided in an embodiment of this application. As shown in Figure 15, the state machine describes the full life cycle process corresponding to a notification message (such as the first notification message) during the sending process as follows: (1) After the first notification message is successfully accepted synchronously, it can be set to the initial state (INIT), and then after the first notification message is processed asynchronously, it can be set to the processing state (PROCESS). Here, synchronous means that the notification center responds synchronously to requests from different business systems; asynchronous means that each notification message in the same business system is processed asynchronously (i.e., different notification messages are processed in different transaction programs). (2) Further, based on the result of the above asynchronous processing, the status of the first notification message may be switched to the successful sending status (SUCCESS) or the failed sending status (FAILURE). (3) If the first notification message has an abnormal situation in the above processing status (PROCESS), and the number of retries corresponding to the current first notification message does not exceed the preset number threshold or the retry time does not exceed the preset time threshold, then the status of the first notification message will be switched to the retry sending status (RETRY) to continue retrying the sending process of the first notification message. (4) If the number of retries of the first notification message is greater than the preset number threshold or the retry time is greater than the preset time threshold, then the status of the first notification message will be switched to the retry count exceeded failure status (RETRY_FAIL). It should be noted that the successful sending status, failed sending status, and retry count exceeded failure status mentioned above are all termination statuses of the first notification message. The so-called termination status is used to indicate the end of the entire sending process of the first notification message.

[0193] Optionally, the state machine corresponding to the first notification message can be sent to the second terminal device for output. Subsequently, the management object (such as operators) can perform visual management of different states during the sending process of the first notification message based on the state machine received by the second terminal device (for example, operators can view the detailed status of the notification message at any time). Based on this, the embodiments of this application support state management of the entire lifecycle of the notification message sending process through a state machine, which can accurately describe the different states of the notification message during the message sending process, and supports sending the state machine to the second terminal device so that operators can visually manage the status of the notification message based on the state machine.

[0194] In this embodiment, the server (such as a notification center) determines the permitted notification method for any notification message in the business system based on the notification method configuration information provided by the first terminal device and the notification management configuration information provided by the second terminal device. Then, it encapsulates the notification message using the notification template corresponding to the determined notification method and sends the encapsulated notification message to the first terminal device for output. During the above processing of any notification message, techniques such as local transactions, idempotent control, concurrency control, domain models, and state machines can be employed to ensure that notification messages are not resent or missed. This method can conveniently, efficiently, and accurately process notification messages in the business system, improving the user experience and business value.

[0195] The following section elaborates on the business architecture and system interactions involved in the message processing method of this application.

[0196] I. Business Architecture.

[0197] Please refer to Figure 16, which is a schematic diagram of the business architecture of a message processing method provided in an embodiment of this application. As shown in Figure 16, the message processing method provided in this application can be applied to cross-regional business scenarios, such as cross-regional asset transfer scenarios, cross-regional e-commerce scenarios, cross-regional logistics scenarios, cross-regional telecommunications scenarios, etc. As shown in Figure 16, the business functional modules involved in this business architecture mainly include three parts: message method settings, message notification, and notification operation capabilities. Specifically:

[0198] (1) The “Message Method Settings” module is mainly used to set the notification method, which mainly includes: adding notification contact information, modifying notification method, querying the notification method list, and unbinding (i.e. deleting) notification method.

[0199] (2) The “Message Notification” module is mainly used to classify the message types of notification messages in the business system. It mainly includes notification messages of different message types such as audit notification, payment reminder, transaction result, welfare information, etc.

[0200] (3) The “Notification Operation Capability” module is mainly used to provide operational management capabilities for business systems. It mainly includes capabilities such as channel gateway configuration, notification scenario configuration, and notification template configuration. The channel gateway is an intermediate component used to connect different notification methods and external channels. Each notification method (such as SMS, email, APP notification, in-app message, etc.) corresponds to a different channel gateway, which is responsible for routing notification messages to the corresponding external channels for sending.

[0201] Based on this, the above business architecture can provide multiple business function modules for the business system in cross-regional business scenarios. Each business function module is responsible for its corresponding business function, and each business function module can perform its own duties. In addition, in the same business scenario, the various business function modules can cooperate with each other, thereby providing reliable and effective business services to business objects.

[0202] II. Notification Center Application Architecture.

[0203] In this application, to implement the aforementioned business functions, a new notification center can be established to assume the corresponding responsibilities. For example, a TDMQ distributed message queue can be used to build the system architecture of the notification center. TDMQ is an important component in a distributed architecture, providing basic asynchronous communication capabilities. By decoupling applications, system complexity is reduced, and system availability and scalability are improved. The system architecture of the notification center can run on a server (e.g., server 103 shown in Figure 1).

[0204] In this application, because cross-regional business operations are subject to restrictions on the scope of customer outreach and compliance licenses, a multi-business object deployment approach is required to construct the notification center system architecture. The notification center supports deployment across multiple business objects, allowing for rapid expansion to other business objects based on business needs, thus meeting the diverse requirements of each. Furthermore, this multi-business object deployment approach enables the notification center to provide independent notification services for each business object; each business object has its own corresponding notification template, configuration, and data, ensuring data isolation and security. This approach satisfies the personalized needs of different business objects while guaranteeing their independence.

[0205] Please refer to Figure 17, which is a schematic diagram of an application architecture for a notification center provided in an embodiment of this application. As shown in Figure 17, the application architecture of this notification center mainly includes:

[0206] (1) Access layer: responsible for accessing the PC front-end, mini-program front-end, and business system corresponding to the business object.

[0207] (2) Service layer: This layer provides service interfaces for requests from various business systems. These service interfaces include, but are not limited to: query notification method list interface, modify notification method interface, notification acceptance RPC (remote procedure call) interface, and notification acceptance message queue.

[0208] (3) Capability Layer: Provides business systems with: notification method management capabilities, notification message acceptance capabilities, notification message processing capabilities, notification operation capabilities, etc., among which:

[0209] 1. Notification method management capabilities include: adding notification methods, modifying notification methods, querying the list of notification methods, and unbinding notification methods;

[0210] 2. Notification message acceptance capability: This refers to the ability to accept any notification message from the business system; it includes: synchronous acceptance via RPC interface (synchronous acceptance means that the notification center responds to requests from different business systems synchronously), asynchronous acceptance via message queue (asynchronous acceptance means that various notification messages from the same business system are processed asynchronously), idempotent control, and other capabilities.

[0211] 3. Notification message processing capabilities include: the ability to process notification messages; these mainly include: asynchronous message queue processing, state machine-driven processing, concurrency control, exception retry, channel routing, and other capabilities.

[0212] 4. Notification operation capabilities include: channel gateway configuration, notification scenario configuration information, notification template configuration information, message operation management, and other capabilities.

[0213] (4) Model layer: used to build various domain models such as notification method information model, notification management model, and notification template information model.

[0214] Based on this, the aforementioned system architecture for the notification center supports distributed deployment of multiple business objects, enabling separate services for each object to flexibly meet their individual needs. Furthermore, the notification center should possess rapid horizontal scaling capabilities to cope with business growth and changes. Horizontal scaling increases the processing capacity and volume of the notification center, ensuring stability and reliability under high load and large-scale business scenarios. This satisfies the notification requirements of different business objects and guarantees high availability and performance of the system.

[0215] III. Interaction sequence diagram of notification method settings.

[0216] Please refer to Figure 18, which is an interaction sequence diagram of a notification method setting provided in an embodiment of this application. As shown in Figure 18, this interaction sequence diagram of the notification method setting is used to describe the interaction flow of a first service object in a first terminal device custom setting a notification method. The specific interaction flow is as follows:

[0217] 1.1 For business objects (such as the first business object), click the notification message settings tab in the front end (first terminal device).

[0218] 1.2 The front end requests the query notification message list interface from the industry portal; whereby the industry portal refers to an online platform that centrally provides information, services and resources within a specific industry or field. In this embodiment, the industry portal may refer to a device (such as a service device) of an online service platform corresponding to cross-regional business.

[0219] 1.3 The industry portal requests the notification message list query interface from the notification center.

[0220] 1.4 The notification center performs parameter verification on the above requests.

[0221] 1.5 The notification center requests data from the notification center DB (Data Base).

[0222] 1.6 Notification Center Assembles Data.

[0223] 1.7 The notification center returns data to the industry portal.

[0224] 1.8 The industry portal returns data to the front end.

[0225] 1.9 The front end returns data to the business object.

[0226] 2.1 The business object requests authentication from the front end.

[0227] 2.2 The front end requests the OTP (One-Time Password) verification interface from the industry portal.

[0228] 2.3 The industry portal requests the verification code service for OTP verification.

[0229] 2.4 The CAPTCHA service undergoes anti-frequent request and anti-fraud strategy verification. Whether OTP verification is required can be determined based on business assessment. OTP verification is a password verification process that uses a password only once. Once used, the password becomes invalid and cannot be reused. If OTP verification is required, the CAPTCHA service must be requested to perform OTP verification, and anti-frequent request and anti-fraud strategy verification must be performed simultaneously to prevent malicious frequent requests or fraudulent operations.

[0230] 2.5 The CAPTCHA service returns the verification results to the industry portal.

[0231] 2.6 The industry portal returns the verification results to the front end.

[0232] 2.7 The front end returns the verification result to the business object.

[0233] 3.1 The business object clicks "Next" in the front end.

[0234] 3.2 The front-end requests the interface to obtain the WeChat Official Account QR code link from the industry portal.

[0235] 3.3 The industry portal generates a cache key and requests parameter information from the cache service. The binding process for social notifications is asynchronous and multi-step, involving multiple operations on business objects and callback notifications from the open platform. Therefore, a cache key is generated to store the request information when a public account QR code is generated, and this cache key is continuously passed through the notification center's modification notification method interface. The open platform refers to a platform that provides open interfaces and services, allowing third-party developers to access and develop applications. In this application, the open platform is used to provide services such as public account QR codes and handling public account binding result callbacks, supporting the social notification binding process. A cache key is a key-value pair used to uniquely identify cached data in the cache service. In the social notification binding process of this application, a cache key is generated to store request information, and this cache key is continuously passed through the notification center's modification notification method interface so that subsequent operations can accurately obtain relevant information.

[0236] 3.4 The industry portal requests the official account QR code from the gateway and carries the cache key parameter.

[0237] 3.5 The gateway requests the official account's QR code from the open platform, carrying the cache key parameter.

[0238] 3.6 The industry portal returns a QR code link to the official account to the front end.

[0239] 3.7 The front end displays the official account QR code link to the business object.

[0240] 4.1 Business users follow the official account.

[0241] 4.2 The open platform sends a callback notification to the gateway to inform the public account of the binding result and carries the cache key parameter.

[0242] 4.3 The gateway sends a public account binding event to the business object.

[0243] 4.4 Confirm the binding of business objects.

[0244] 4.5 The front-end obtains the platform's personal avatar from the open platform.

[0245] 4.6 The front end displays avatars to business objects.

[0246] 4.7 Set nicknames and avatars for business objects.

[0247] Among them, steps 2.1-4.7 above are the operation flow corresponding to an opt (option). For example, if the option is: "User selects to bind social APP", then the corresponding operation flow is the process shown in steps 2.1-4.7 above.

[0248] 5.1 Notification methods for adding / editing / deleting business objects on the front end.

[0249] 5.2 The front-end requests the interface to modify the notification method from the industry portal.

[0250] 5.3 The industry portal requests the notification center to modify the notification method interface.

[0251] 5.4 The notification center performs parameter validation on requests; when modifying notification method parameter validation, in addition to basic business parameter validation and business object identity information validation, it is also necessary to validate the number of newly added notification methods to ensure that the number of newly added notification methods is less than the total number allowed by the business.

[0252] 5.5 The notification center requests the verification code service to perform OTP verification.

[0253] 5.6 Verify the anti-frequent and anti-fraud strategies for the CAPTCHA service.

[0254] 5.7 The verification code service returns the verification result to the notification center.

[0255] Among them, steps 5.5-5.7 above are the operation flow corresponding to an opt (option). For example, if the option is: "OTP verification required", then the corresponding operation flow is the process shown in steps 5.5-5.7 above.

[0256] 5.8 The notification center queries cached information based on the cache key.

[0257] 5.9 The notification center requests the public account openid from the gateway.

[0258] 5.10 The gateway requests the WeChat Official Account's openid from the open platform.

[0259] 5.11 The gateway returns the public account openid to the notification center.

[0260] Among them, steps 5.8-5.11 above are the operation flow corresponding to an opt (option). For example, if the option is: "Add APP notification method", then the corresponding operation flow is the process shown in steps 5.8-5.11 above.

[0261] 5.12 Notification Center requests risk control strategy consultation; among them, modifying the notification method requires requesting risk control strategy consultation to ensure effective response to business risks and challenges.

[0262] 5.13 The notification center handles changes to notification method configuration information based on the operation type; in specific implementation, the notification method information model change information can be assembled according to the strategy mode when adding, editing, or unbinding operations.

[0263] 5.14 Notification Center Persistent Domain Model.

[0264] 5.15 The Notification Center returns results to the industry portal.

[0265] 5.16 The industry portal returns results to the front end.

[0266] Based on this, the aforementioned interactive process for customizing notification methods supports business objects in setting multiple notification methods, and allows for prioritizing business function modules that need to receive messages. Even if a certain notification method is unavailable, business objects can still receive notification messages in a timely manner through other means, avoiding missing important information due to the failure of a single notification method. This flexible setting method can improve message attention and processing efficiency, while avoiding interference caused by receiving a large number of irrelevant messages, thus improving the business experience.

[0267] IV. Sequence diagram of message notification interaction.

[0268] In cross-regional business scenarios, where service providers need to send notification messages to business objects, each business system corresponding to its respective business domain requests the notification center to send the notification messages uniformly. The notification center provides two access methods: synchronous RPC (Remote Procedure Call) interface calls and asynchronous TDMQ message subscriptions. Please refer to Figure 19, which is an interaction sequence diagram of a message notification provided in an embodiment of this application. As shown in Figure 19, this message notification interaction sequence diagram describes the interaction flow for sending notification messages, and its specific interaction flow is as follows:

[0269] I. **Simultaneous Processing** (1.1-2.4):

[0270] 1.1 The business system requests the notification center to send a notification message.

[0271] 1.2 The notification center performs parameter verification. This parameter verification includes: the notification center verifying basic business parameters of the interface contract, and also verifying the identity information of the business object (e.g., permission verification, validity verification, etc.) to ensure that the business object's account registered with the service provider is valid.

[0272] 1.3 The notification center requests notification template configuration information from the notification center DB based on the notification time and notification scenario.

[0273] 1.4 The notification center DB returns notification template configuration information to the notification center.

[0274] 1.5 The notification center performs notification template configuration information verification. This verification checks whether the corresponding notification template is configured in the second terminal device and whether the notification message parameters passed in the service request match the message format of the notification template.

[0275] 1.6 Query notification method configuration information based on merchant information (such as the notification identifier of the first business object).

[0276] 1.7 The notification center performs idempotency checks.

[0277] 1.8 The notification center requests the notification center DB to query the previous processing result.

[0278] 1.9 Consistency check of parameters in two consecutive requests to the notification center.

[0279] 1.10 The notification center returns the previous processing result to the business system.

[0280] Among them, steps 1.8-1.10 above belong to the operation flow corresponding to an opt (option). For example, if the option is "Hit Idempotent", then the corresponding operation flow is the process shown in steps 1.8-1.10 above.

[0281] 1.11 The notification center assembles the notification management aggregate root identifier. When assembling the notification management aggregate root identifier, both the notification acceptance number and the notification record number are generated using a distributed ID generation method. Distributed ID generation is a method for generating unique IDs in a distributed system, ensuring that IDs generated across different nodes and services are unique. In this application, both the notification acceptance number and the notification record number are generated using a distributed ID generation method to guarantee the uniqueness of these numbers in a distributed environment.

[0282] 1.12 Domain Model for Persistent Notification Management in Notification Centers

[0283] 1.13 The notification center writes the notification record number to TDMQ (a distributed message queue). This step can be executed in a loop; that is, as long as the notification record number exists in the produced notification record message, the notification record number will be written to TDMQ.

[0284] 1.14 The notification center returns the notification acceptance result to the business system.

[0285] Steps 1.7-1.13 above are all executed within the same transaction program (such as the first transaction program). This first transaction program runs local transactions and ensures that all database operations of the notification management domain model satisfy ACID properties through local transactions. Furthermore, it ensures strong consistency between the database operations and message queues of the notification management domain model through transactional messages. Transactional messages are a messaging mechanism used to guarantee transaction consistency. In this application, transactional messages ensure strong consistency between the database operations and message queues of the notification management domain model; that is, either all related operations execute successfully, or none execute, thus guaranteeing data integrity.

[0286] In addition, steps 1.7-1.10 above are executed using an idempotent control strategy. Idempotent control is implemented through a unique index on the notification acceptance form. The idempotent control fields are the request serial number ID (business order number, such as a withdrawal order number) generated by the business system and the notification scenario. Furthermore, after idempotency is achieved, the consistency of the parameters in the two requests needs to be verified. The idempotent control strategy ensures that the notification message only needs to be sent to the business object once, guaranteeing that the notification message is not resent.

[0287] 2.1 If the notification center returns an error message indicating that the business system has accepted the request and the request is resent, the business system will resend the request to TDMQ (the processing flow is the same as steps 1.2-1.14 above).

[0288] 2.2 Business system production notification acceptance message.

[0289] 2.3 Notification Center Subscription Notification Received Messages.

[0290] The above steps 2.1-2.3 are executed using an exception compensation mechanism. That is, when the business system calls the notification center abnormally, it can compensate by either capturing the exception and resending the notification or sending a notification acceptance message.

[0291] 2.4 The notification center processes the notification acceptance messages (the processing procedure is the same as steps 1.2-1.14 above).

[0292] Among them, 2.1-2.4 above belong to the operation process corresponding to an opt (option). For example, if the option is: "Notification center returns business system acceptance exception and resends exception", then the corresponding operation process is the process shown in steps 2.1-2.4 above.

[0293] II. [Asynchronous Processing] Flowchart (3.1-3.16):

[0294] 3.1 Notification Center Subscribes to Notification Record Messages. Synchronous processing generates a notification record message upon successful acceptance, while asynchronous processing is handled by subscribing to notification record messages.

[0295] 3.2 The notification center locks the notification center database to query notification records.

[0296] 3.3 Notification Center Sending Status Validity Judgment.

[0297] 3.4 The notification center updates the sending status to "Processing Status".

[0298] The above steps 3.2-3.4 are executed using a concurrency control strategy, and all operations involved in steps 3.2-3.4 must be performed within the same transaction program. Furthermore, the principle of state machine change follows the sequence of lock, decision, and update.

[0299] 3.5 Notification Method Gateway Routing. Each notification method (such as SMS, email, app notification, in-app message, etc.) corresponds to a different notification gateway channel. This step uses a policy pattern to route notifications to the corresponding notification gateway channel based on the notification method.

[0300] 3.6 Send messages via the gateway using the notification method.

[0301] 3.7 Notification Method: The gateway returns the sending result to the notification center.

[0302] 3.8 The notification center processes the sending results.

[0303] 3.9 Lock the Notification Center to query notification records.

[0304] 3.10 Notification Center Sending Status Validity Check.

[0305] 3.11 If the status of the notification message is explicitly stated as either "sent successfully" or "sent failed", the notification center will update the sending status to "success or failure".

[0306] 3.12 If the status of the call exception or error code non-explicit notification message is a failure status, the notification center requests to query the notification scenario configuration information.

[0307] 3.13 Determine if a retry is needed. Different business scenarios may have different requirements when handling message retries due to exceptions. To avoid infinite retries, if the number of retries exceeds a preset threshold or the retry time exceeds a preset time threshold, it is determined that a retrieval is not needed, and the sending status is updated to a retry failure status.

[0308] 3.14 If retry is not required, update the sending status to "Retry Failed".

[0309] 3.15 If a retry is required, update the sending status to "Retry Status" and increment the retry count by 1.

[0310] 3.16 If the number of retries for a notification message reaches the maximum allowed by the MQ (i.e., TDMQ), the business system will regenerate the notification record message and generate a new message ID. Because TDMQ has a limit on the number of retries per notification message, if it is determined that the current notification message needs to be retried and the number of retries for this notification message exceeds the maximum allowed by TDMQ, the status of the notification message should be switched to the retry exceeded failure status, and the notification record message should not be regenerated.

[0311] In this process, steps 3.11-3.16 constitute an alt operation. The alt operator indicates the "if...else..." decision logic; that is, if the message status is explicitly stated as either successfully sent or failed, then the process described in steps 3.11-3.16 is executed. Similarly, steps 3.14-3.16 also constitute an alt operation; that is, if the message status is explicitly stated as not requiring retries, then the process described in steps 3.14-3.16 is executed. Additionally, step 3.16 is an opt operation. For example, if the option is set to "The number of retries for the notification message has reached the maximum allowed number of retries by the MQ (i.e., TDMQ)," then step 3.16 is executed.

[0312] III. [Abnormal Retry] Process (4.1-4.4):

[0313] 4.1 If the number of retries required for a notification message reaches the maximum allowed by the MQ (i.e., TDMQ), the business system will subscribe to the notification record message from TDMQ (the processing flow is the same as the subsequent steps in 3.1).

[0314] 4.2 The notification center throws a system exception to TDMQ.

[0315] 4.3 TDMQ catches exceptions and retryes.

[0316] 4.4 The business system subscribes to notification log messages from TDMQ (the processing flow is the same as the subsequent steps in 3.1).

[0317] In addition, steps 4.1-4.4 above constitute an opt (option) operation process. For example, the option is: the notification message needs to be retried to reach the maximum number of retries allowed by MQ (i.e., TDMQ). The corresponding operation process is the process shown in steps 4.1-4.4 above.

[0318] Based on this, in the above-mentioned interactive process of sending notification messages, by adopting a variety of technical strategies such as local transactions, transactional messages, idempotent control, concurrency control, exception retries and automatic compensation, the reliability of the message notification process can be improved by ensuring that notification messages are not missed or resent throughout the entire message notification chain.

[0319] V. Interaction sequence diagram of notification operation capabilities.

[0320] Specifically, the notification operation capability provides service provider operators (such as the second business entity) with a platform for centralized management and operation of cross-regional business notification messages. It supports better configuration, management, and querying of notification message sending status. Service provider operators can configure notification scenario information, notification template information, and manage message operations. Please refer to Figure 20, which is an interaction sequence diagram of a notification operation capability provided in an embodiment of this application. As shown in Figure 20, the interaction sequence diagram of this notification operation capability describes the interaction process for operating and managing the business system. The specific interaction process is as follows:

[0321] (1) Information configuration process for notification scenarios:

[0322] 1.1.1 Operations personnel can click to query the list of notification scenario configuration information on the operations page (message notification management interface).

[0323] 1.1.2 Request the interface to query the list of notification scenario configuration information from the operation front-end (second terminal device).

[0324] 1.1.3 The operation frontend requests the interface for querying the list of notification scenario configuration information from the operation backend (the backend device corresponding to the second terminal device).

[0325] 1.1.4 The operations backend requests data from the notification center DB.

[0326] 1.1.5 Assemble data for the operation backend.

[0327] 1.1.6 The operations backend returns data to the operations frontend.

[0328] 1.1.7 The operations frontend returns data to the operations page.

[0329] 1.1.8 Display notification scenario configuration information to business objects.

[0330] 1.2.1 Operations personnel can click to view the details of the notification scenario configuration information.

[0331] 1.2.2 Request the interface for querying the details of the notification scenario configuration information from the operations front end.

[0332] 1.2.3 The operation frontend requests the interface for querying the details of the notification scenario configuration information from the operation backend.

[0333] 1.2.4 The operations backend requests data from the notification center DB.

[0334] 1.2.5 Assemble data for the operation backend.

[0335] 1.2.6 The operations backend returns data to the operations frontend.

[0336] 1.2.7 The operations front-end returns data to the operations page.

[0337] 1.2.8 Display notification scenario configuration information to business objects.

[0338] 1.3.1 Add / edit notification scenario configuration information.

[0339] 1.3.2 Request the interface to modify the configuration information of the notification scenario from the operation front end.

[0340] 1.3.3 Interface for the operations front-end to request modification of notification scenario configuration information from the operations back-end.

[0341] 1.3.4 The operations backend requests data modification from the notification center DB.

[0342] 1.3.5 The operations backend returns data to the operations frontend.

[0343] 1.3.6 The operations front-end returns data to the operations page.

[0344] 1.3.7 Display notification scenario configuration information.

[0345] (2) Notification template information configuration process:

[0346] 2.1.1 Click to view the list of notification template configuration information.

[0347] 2.1.2 Request the interface to query the list of notification template configuration information from the operations front-end.

[0348] 2.1.3 The operations frontend requests the list of notification template configuration information from the operations backend via an interface.

[0349] 2.1.4 The operations backend requests data from the notification center database.

[0350] 2.1.5 Assemble data for the operation backend.

[0351] 2.1.6 The operations backend returns data to the operations frontend.

[0352] 2.1.7 The operations frontend returns data to the operations page.

[0353] 2.1.8 Display notification template configuration information to business objects.

[0354] 2.2.1 Operations personnel can click to view the details of the notification template configuration information.

[0355] 2.2.2 Request the interface for querying notification template configuration details from the operations frontend.

[0356] 2.2.3 The operations frontend requests the details of the notification template configuration information from the operations backend interface.

[0357] 2.2.4 The operations backend requests data from the notification center DB.

[0358] 2.2.5 Assemble data for the operation backend.

[0359] 2.2.6 The operations backend returns data to the operations frontend.

[0360] 2.2.7 The operations frontend returns data to the operations page.

[0361] 2.2.8 Display notification template configuration information to business objects.

[0362] 2.3.1 Add / edit notification template configuration information.

[0363] 2.3.2 Request the interface to modify the notification template configuration information from the operations front end.

[0364] 2.3.3 Interface for the operations front-end to request modification of notification template configuration information from the operations back-end.

[0365] 2.3.4 The operations backend requests data modification from the notification center DB.

[0366] 2.3.5 The operations backend returns data to the operations frontend.

[0367] 2.3.6 The operations front-end returns data to the operations page.

[0368] 2.3.7 Display notification template configuration information.

[0369] (3) The operation and management process of notification messages:

[0370] 3.1.1 Operations personnel request to query notification message sending records.

[0371] 3.1.2 Request the query notification record list interface from the operations front end.

[0372] 3.1.3 The operations frontend requests the interface for querying the list of notification records from the operations backend.

[0373] 3.1.4 The operations backend requests data from the notification center DB.

[0374] 3.1.5 Assemble data for the operation backend.

[0375] 3.1.6 The operations backend returns data to the operations frontend.

[0376] 3.1.7 The operations front-end returns data to the operations page.

[0377] 3.1.8 Display notification record data to business users.

[0378] 3.2.1 Operations personnel upload message files that are manually sent in batches.

[0379] 3.2.2 Request the batch message file parsing interface from the operations front-end.

[0380] 3.2.3 The operations frontend requests the batch message file parsing interface from the operations backend.

[0381] 3.2.4 Operation backend parsing file.

[0382] 3.2.5 The operations backend sends batch production notification messages to TDMQ.

[0383] 3.2.6 The operations center subscribes to TDMQ to receive notification messages.

[0384] 3.2.7 The operations backend returns results to the operations frontend.

[0385] 3.2.8 The operations front-end returns results to the operations page.

[0386] 3.2.9 Display the returned results to the business object.

[0387] Based on this, in the above-mentioned interactive process of operation management, on the one hand, it supports operators to customize the notification templates corresponding to the notification scenarios and notification methods applicable to the business system, thereby meeting the flexibility needs of different business systems in different business scenarios; on the other hand, it supports sending message files in batches to various business objects in special scenarios such as abnormalities in the business system (such as network outages) or holidays, which can provide operators with more efficient notification management capabilities, thereby improving the convenience and efficiency of the notification management process.

[0388] The following describes the relevant apparatus of the message processing scheme provided in the embodiments of this application.

[0389] It should be noted that, in the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program with a predetermined function, which works together with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0390] Please refer to Figure 21, which is a schematic diagram of a message processing device provided in an embodiment of this application. This message processing device 2100 can be used to execute the corresponding steps in the message processing method provided in the embodiment of Figure 3 of this application. Specifically, the message processing device 2100 may include:

[0391] Display unit 2101 is used to display message notification setting interface, which is used to set the notification method for business system.

[0392] Processing unit 2102 is configured to, in response to the first setting operation, set notification method configuration information for the business system, wherein the notification method configuration information is used to indicate M1 notification methods, and M1 is a positive integer;

[0393] The output unit 2103 is used to output the first notification message in one of the M1 set notification methods when the first notification message is received from the business system.

[0394] In one possible implementation, the above method is applied to a first terminal device, which is a terminal device used by a first business object in the business system; the processing unit 2102 is also used to perform the following operations:

[0395] Based on the object type of the first business object, display N configuration items that match the object type of the first business object. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1.

[0396] The method for classifying the object type of the first business object includes at least one of the following: classifying according to the geographical scope of the first business object, classifying according to the permission level of the first business object in the business system, and classifying according to the business scope operated by the first business object.

[0397] In one possible implementation, the processing unit 2102 is further configured to perform the following operations:

[0398] Based on the system type of the business system, display N configuration items that match the system type of the business system. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1;

[0399] The classification methods for business system types include at least one of the following: classification according to the business functions of the business system, classification according to the business scope of the business system, and classification according to the geographical scope involved in the business functions of the business system.

[0400] In one possible implementation, the first setting operation includes triggering the first configuration item among N configuration items, where the first configuration item is any one of the N configuration items; the first configuration item is used to set the first notification method; the notification method configuration information includes sub-configuration information of the first notification method;

[0401] In response to the first setting operation, the processing unit 2102 sets the notification method configuration information for the business system, for performing the following operations:

[0402] In response to a trigger operation on the first configuration item, the system receives parameter information from the configuration fields of the first configuration item. The configuration fields of the first configuration item include a first notification identifier field and a first notification content field.

[0403] Based on the parameter information of the configuration fields in the first configuration item, generate sub-configuration information for the first notification method;

[0404] The first notification identifier field is used to set the notification identifier to which the notification message is output to the business object when the notification message is output according to the first notification method; the first notification content field is used to set the message type of the notification message output according to the first notification method.

[0405] In one possible implementation, the processing unit 2102 is further configured to perform the following operations:

[0406] In response to a notification method change event, update the notification method configuration information; the notification method change event includes at least one of the following: the first business object in the business system performs an editing operation on the sub-configuration information of any of the M1 notification methods, the object type of the first business object changes, and the system type of the business system changes;

[0407] Among them, the business system is applied in cross-regional business scenarios, which means that the execution of the business involves at least two different regions.

[0408] This application provides a message processing solution that supports business objects in customizing at least one notification method. On one hand, business objects can visually set the notification method of the business system through a message notification settings interface, improving the flexibility of notification method settings and business interactivity. On the other hand, this application also supports business objects in customizing at least one notification method (such as SMS, email, social apps, etc.), which can meet the actual notification needs of business objects. Different business objects can personalize their notification methods according to their own needs, improving business convenience and flexibility. Furthermore, notification messages in the business system can be output according to at least one notification method customized by the business object. This ensures that notification messages are processed according to the actual notification needs of the business object, guaranteeing convenient, efficient, and accurate output. Consequently, business objects can receive and process notification messages in the business system in a timely manner, improving business processing efficiency.

[0409] Please refer to Figure 22, which is a schematic diagram of another message processing device provided in an embodiment of this application. This message processing device 2200 can be used to execute the corresponding steps in the message processing method provided in the embodiment of Figure 9 in this application. Specifically, the message processing device 2200 may include:

[0410] Display unit 2201 is used to display message notification management interface. The message notification management interface is used to perform notification management operations on the business system. The notification management operations include the second setting operation.

[0411] Processing unit 2202 is used to set the notification message configuration information of the business system in response to the second setting operation. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method. M2 is a positive integer.

[0412] Sending unit 2203 is used to send notification messages to business objects in the business system according to the notification message configuration information of the business system.

[0413] In one possible implementation, the notification scenario includes at least one notification event. Each notification event belongs to a business function module in the business system. Whenever any business function module in the business system is triggered to generate a corresponding notification event, a notification message needs to be sent to the business object in the business system. The notification message corresponding to each notification event supports output using at least one notification method.

[0414] The notification scenario configuration information includes at least one of the following: description information of the notification scenario, description information of the notification event in the notification scenario, identifier of the business function module corresponding to the notification event, object type of the business object being notified, identifier of the M2 notification methods configured for the notification event, number of retries when the notification message is sent, and retry time when the notification message is sent.

[0415] The notification template configuration information includes at least one of the following: description of the applicable notification scenario, description of the applicable notification event, identifier of the applicable business function module, identifier of the applicable notification method, and description of the notification template; the description of the notification template includes the identifier of the notification template, the message format of the notification template, and the validity period of use.

[0416] In one possible implementation, the management operation further includes a batch notification operation; the processing unit 2202 is also used to perform the following operations:

[0417] In response to a batch notification operation, a message file is received. The message file contains the message content of the target message to be batch notified and batch notification description information. The batch notification description information includes at least one of the following: the type of business object of the batch notification, the identifier of the notification method used by the batch notification, and the description information of the notification template corresponding to the notification method used by the batch notification.

[0418] Batch notification processing of target messages is performed according to the message file.

[0419] In this embodiment, a message notification management interface can be displayed, providing operators with notification operation capabilities for the business system. This notification operation capability provides operators with a centralized platform for managing and operating notification messages, enabling them to better configure, manage, and query the sending status of notification messages. Operators can conveniently configure notification scenario configuration information, notification template configuration information, and other notification message configuration information within the message notification interface. This method of managing notification operations for the business system through an intuitive visual interface (message notification management interface) improves the efficiency and convenience of notification operation management.

[0420] Please refer to Figure 23, which is a schematic diagram of another message processing device provided in an embodiment of this application. This message processing device 2300 can be used to execute the corresponding steps in the message processing method provided in the embodiment of Figure 12 of this application. Specifically, the message processing device 2300 may include:

[0421] The acquisition unit 2301 is used to acquire notification method configuration information for the business system from the first terminal device. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer.

[0422] The acquisition unit 2301 is also used to acquire notification message configuration information of the business system from the second terminal device. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method. M2 is a positive integer.

[0423] Processing unit 2302 is used to encapsulate and process the first notification message in the business system based on notification method configuration information and notification message configuration information;

[0424] The sending unit 2303 is used to send the encapsulated first notification message to the first terminal device for output.

[0425] In one possible implementation, the processing unit 2302 encapsulates the first notification message in the business system based on the notification method configuration information and the notification message configuration information, for the following operations:

[0426] Based on the notification method configuration information and the notification message configuration information, M3 notification methods to be used for the first notification message are determined; wherein, the M3 notification methods are the intersection of the M1 notification methods and the M2 notification methods, and M3 is a positive integer;

[0427] The first notification message is encapsulated and processed according to the notification templates corresponding to the M3 notification methods.

[0428] In one possible implementation, after encapsulation, M3 first notification messages are obtained, each corresponding one-to-one with one of the M3 notification methods. The processing unit 2302 sends the encapsulated notification messages to the first terminal device for output, to perform the following operations:

[0429] In the first transaction procedure, prepare for the sending of the first notification message M3;

[0430] An idempotent control strategy is used to control the sending operation in the first transaction procedure so that one of the M3 first notification messages is sent to the first terminal device for output.

[0431] In one possible implementation, the business system also includes a second notification message. After encapsulation, the second notification message is processed to obtain M3 second notification messages, each corresponding one-to-one with one of the M3 notification methods. The processing unit 2302 is also used to perform the following operations:

[0432] The sending operation of the second notification message M3 is performed in the second transaction procedure; the second transaction procedure is a different transaction procedure from the first transaction procedure;

[0433] A concurrency control strategy is adopted to send the first notification message and the second notification message concurrently to the first terminal device for output.

[0434] In one possible implementation, the processing unit 2302 is further configured to perform the following operations:

[0435] Obtain the state machine generated during the sending of the first notification message; wherein, the state machine is used to describe the different states corresponding to the first notification message during the sending process;

[0436] The state machine corresponding to the first notification message is sent to the second terminal device for output.

[0437] The states described by the state machine include: start state, processing state, successful transmission state, failed transmission state, retry transmission state, and retry limit failure state.

[0438] In one possible implementation, the processing unit 2302 is further configured to perform the following operations:

[0439] Obtain the domain model, which includes the notification management model, the notification template information model, and the notification method information model;

[0440] The notification method information model is invoked to manage the notification method configuration information, the notification template information model is invoked to manage the notification message configuration information, and the notification management model is invoked to manage the sending process of the first notification message in the business system.

[0441] In this architecture, each domain model adopts an aggregate design approach to construct its management structure. Each domain model has its own aggregate root identifier, and each domain model interacts with other domain models through the aggregate root identifier during its management process.

[0442] In this embodiment, based on the notification method configuration information provided by the first terminal device and the notification management configuration information provided by the second terminal device, the allowed notification method for any notification message in the business system is determined. Then, the notification message is encapsulated based on the notification template corresponding to the determined notification method, and the encapsulated notification message is sent to the first terminal device for output. During the above processing of any notification message, techniques such as local transactions, idempotent control, concurrency control, domain models, and state machines can be employed to ensure that notification messages are not resent or missed. This method can conveniently, efficiently, and accurately process notification messages in the business system, improving the user experience and business value.

[0443] Please refer to Figure 24, which is a schematic diagram of the structure of a computer device provided in an embodiment of this application. The computer device 2400 is used to execute the steps performed by the computer device (such as a first terminal device, a second terminal device, or a server) in the aforementioned method embodiments. The computer device 2400 may include one or more devices (such as a server, node, terminal device, etc.) and internal components (such as chips, software modules, or hardware modules). The computer device may include at least one processor 2401 and a communication interface 2402. Further optionally, the computer device may also include at least one memory 2403 and a bus 2404. Additionally, the processor 2401, communication interface 2402, and memory 2403 are connected via the bus 2404.

[0444] (1) The processor 2401 is a module that performs arithmetic and / or logical operations. Specifically, it may be one or a combination of processing modules such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor unit (MPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), a coprocessor (to assist the central processing unit in completing corresponding processing and applications), and a micro controller unit (MCU).

[0445] (2) The communication interface 2402 can be used to provide information input or output to at least one processor 2401. And / or, the communication interface 2402 can be used to receive data sent externally and / or send data externally, and can be a wired link interface including such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, vehicle short-range communication technology, and other short-range wireless communication technologies, etc.). The communication interface 2402 can serve as a network interface.

[0446] (3) The memory 2403 is used to provide storage space, in which data such as the operating system and computer programs (including program instructions) can be stored. The memory 2403 can be one or a combination of random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc.

[0447] In specific implementation, when the computer device is the first terminal device, the processor 2401 executes the following steps by running the computer program stored in the memory 2403:

[0448] Displays the message notification settings interface, which is used to configure the notification method for the business system;

[0449] In response to the first setting operation, the notification method configuration information for the business system is set. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer.

[0450] When the first notification message is received from the business system, the first notification message is output in the M1 configured notification methods.

[0451] In one possible implementation, the above method is applied to a first terminal device, which is a terminal device used by a first business object in the business system; the processor 2401 is also used to perform the following operations:

[0452] Based on the object type of the first business object, display N configuration items that match the object type of the first business object. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1.

[0453] The method for classifying the object type of the first business object includes at least one of the following: classifying according to the geographical scope of the first business object, classifying according to the permission level of the first business object in the business system, and classifying according to the business scope operated by the first business object.

[0454] In one possible implementation, processor 2401 is also used to perform the following operations:

[0455] Based on the system type of the business system, display N configuration items that match the system type of the business system. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1;

[0456] The classification methods for business system types include at least one of the following: classification according to the business functions of the business system, classification according to the business scope of the business system, and classification according to the geographical scope involved in the business functions of the business system.

[0457] In one possible implementation, the first setting operation includes triggering the first configuration item among N configuration items, where the first configuration item is any one of the N configuration items; the first configuration item is used to set the first notification method; the notification method configuration information includes sub-configuration information of the first notification method;

[0458] In response to the first setting operation, processor 2401 sets notification method configuration information for the business system to perform the following operations:

[0459] In response to a trigger operation on the first configuration item, the system receives parameter information from the configuration fields of the first configuration item. The configuration fields of the first configuration item include a first notification identifier field and a first notification content field.

[0460] Based on the parameter information of the configuration fields in the first configuration item, generate sub-configuration information for the first notification method;

[0461] The first notification identifier field is used to set the notification identifier to which the notification message is output to the business object when the notification message is output according to the first notification method; the first notification content field is used to set the message type of the notification message output according to the first notification method.

[0462] In one possible implementation, processor 2401 is also used to perform the following operations:

[0463] In response to a notification method change event, update the notification method configuration information; the notification method change event includes at least one of the following: the first business object in the business system performs an editing operation on the sub-configuration information of any of the M1 notification methods, the object type of the first business object changes, and the system type of the business system changes;

[0464] Among them, the business system is applied in cross-regional business scenarios, which means that the execution of the business involves at least two different regions.

[0465] II. In specific implementation, when the computer device is a second terminal device, the processor 2401 executes the following steps by running the computer program stored in the memory 2403:

[0466] The message notification management interface is displayed. The message notification management interface is used to perform notification management operations on the business system. The notification management operations include the second setting operation.

[0467] In response to the second setting operation, the notification message configuration information of the business system is set; the notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system; the notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer.

[0468] According to the notification message configuration information of the business system, send notification messages to the business objects in the business system.

[0469] In one possible implementation, the notification scenario includes at least one notification event. Each notification event belongs to a business function module in the business system. Whenever any business function module in the business system is triggered to generate a corresponding notification event, a notification message needs to be sent to the business object in the business system. The notification message corresponding to each notification event supports output using at least one notification method.

[0470] The notification scenario configuration information includes at least one of the following: description information of the notification scenario, description information of the notification event in the notification scenario, identifier of the business function module corresponding to the notification event, object type of the business object being notified, identifier of the M2 notification methods configured for the notification event, number of retries when the notification message is sent, and retry time when the notification message is sent.

[0471] The notification template configuration information includes at least one of the following: description of the applicable notification scenario, description of the applicable notification event, identifier of the applicable business function module, identifier of the applicable notification method, and description of the notification template; the description of the notification template includes the identifier of the notification template, the message format of the notification template, and the validity period of use.

[0472] In one possible implementation, the management operations also include batch notification operations; the processor 2401 is also used to perform the following operations:

[0473] In response to a batch notification operation, a message file is received. The message file contains the message content of the target message to be batch notified and batch notification description information. The batch notification description information includes at least one of the following: the type of business object of the batch notification, the identifier of the notification method used by the batch notification, and the description information of the notification template corresponding to the notification method used by the batch notification.

[0474] Batch notification processing of target messages is performed according to the message file.

[0475] III. In specific implementation, when the computer device is a server (i.e., a notification center), the processor 2401 executes the following steps by running the computer program stored in the memory 2403:

[0476] Obtain notification method configuration information for the business system from the first terminal device. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer.

[0477] The notification message configuration information of the business system is obtained from the second terminal device. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method. M2 is a positive integer.

[0478] Based on the notification method configuration information and notification message configuration information, the first notification message in the business system is encapsulated and processed.

[0479] The encapsulated first notification message is sent to the first terminal device for output.

[0480] In one possible implementation, the processor 2401 encapsulates the first notification message in the business system based on the notification method configuration information and the notification message configuration information, for the following operations:

[0481] Based on the notification method configuration information and the notification message configuration information, M3 notification methods to be used for the first notification message are determined; wherein, the M3 notification methods are the intersection of the M1 notification methods and the M2 notification methods, and M3 is a positive integer;

[0482] The first notification message is encapsulated and processed according to the notification templates corresponding to the M3 notification methods.

[0483] In one possible implementation, after encapsulation, M3 first notification messages are obtained, each corresponding one-to-one with one of the M3 notification methods. The processor 2401 sends the encapsulated notification messages to the first terminal device for output, to perform the following operations:

[0484] In the first transaction procedure, prepare for the sending of the first notification message M3;

[0485] An idempotent control strategy is used to control the sending operation in the first transaction procedure so that one of the M3 first notification messages is sent to the first terminal device for output.

[0486] In one possible implementation, the business system also includes a second notification message. After encapsulation, the second notification message is processed to obtain M3 second notification messages, each corresponding one-to-one with one of the M3 notification methods. The processor 2401 is also used to perform the following operations:

[0487] The sending operation of the second notification message M3 is performed in the second transaction procedure; the second transaction procedure is a different transaction procedure from the first transaction procedure;

[0488] A concurrency control strategy is adopted to send the first notification message and the second notification message concurrently to the first terminal device for output.

[0489] In one possible implementation, processor 2401 is also used to perform the following operations:

[0490] Obtain the state machine generated during the sending of the first notification message; wherein, the state machine is used to describe the different states corresponding to the first notification message during the sending process;

[0491] The state machine corresponding to the first notification message is sent to the second terminal device for output.

[0492] The states described by the state machine include: start state, processing state, successful transmission state, failed transmission state, retry transmission state, and retry limit failure state.

[0493] In one possible implementation, processor 2401 is also used to perform the following operations:

[0494] Obtain the domain model, which includes the notification management model, the notification template information model, and the notification method information model;

[0495] The notification method information model is invoked to manage the notification method configuration information, the notification template information model is invoked to manage the notification message configuration information, and the notification management model is invoked to manage the sending process of the first notification message in the business system.

[0496] In this architecture, each domain model adopts an aggregate design approach to construct its management structure. Each domain model has its own aggregate root identifier, and each domain model interacts with other domain models through the aggregate root identifier during its management process.

[0497] The computer device provided in this application embodiment is used to execute the message processing method mentioned in this application. On the one hand, it supports business objects to customize at least one notification method (such as SMS notification, email notification, social notification, etc.) in the message notification interface, which can meet the actual notification needs of business objects. Moreover, different business objects can realize personalized settings of notification methods according to their own needs, improving business convenience and flexibility. On the other hand, notification messages in the business system can be output according to various notification methods customized by business objects. In this way, the notification messages of the business system can be processed according to the actual notification needs of business objects, ensuring that the notification messages are output conveniently, efficiently, and accurately.

[0498] According to one aspect of this application, embodiments of this application also provide a computer-readable storage medium storing a computer program. When a processor executes the computer program, it can perform the methods described in the preceding embodiments; therefore, further details will not be repeated here. For technical details not disclosed in the embodiments of the computer-readable storage medium involved in this application, please refer to the description of the method embodiments of this application. As an example, the computer program can be deployed on a computer device, or executed on multiple computer devices located in one location, or executed on multiple computer devices distributed in multiple locations and interconnected through a communication network.

[0499] According to one aspect of this application, embodiments of this application also provide a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, enabling the computer device to perform the methods described in the foregoing embodiments; therefore, further details will not be repeated here. For technical details not disclosed in the embodiments of the computer program product involved in this application, please refer to the description of the method embodiments of this application.

[0500] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product, which includes one or more computer programs. When the computer program is loaded and executed on a computer device, it generates, in whole or in part, the processes or functions described in the embodiments of this application; the computer device can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in or transmitted through a computer-readable storage medium; the computer program can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium accessible to the computer device or a data processing device such as a server or data center that integrates one or more available media; wherein, the available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0501] In summary, this application provides a message processing method, apparatus, device, computer-readable storage medium, and computer program product. A first terminal device displays a message notification setting interface for setting notification methods for a business system. Responding to a first setting operation, it sets notification method configuration information for the business system to indicate M1 notification methods. When a first notification message is received from the business system, the message is output using the set M1 notification methods. This multi-method message output mechanism improves message reachability from a technical perspective. In complex network environments or when different business objects use different receiving devices, multiple notification methods increase the probability of successful message delivery to business objects, reduce the risk of message loss, and enhance the system's robustness in communication. Simultaneously, business objects can flexibly set notification methods according to their own needs, reflecting the system's flexibility in user configuration, helping to improve system resource utilization and avoid unnecessary waste of notification resources.

[0502] Furthermore, the first terminal device, used by the first business object in the business system, displays N matching configuration items to set the notification method based on the object type of the first business object. By categorizing object types according to the geographical location of the first business object, its permission level in the business system, and the scope of its operations, from a data matching and personalized service perspective, it is possible to accurately provide suitable configuration items for different types of business objects. This reduces the information filtering cost for business objects when setting notification methods and improves the efficiency of configuration operations. Moreover, through this precise matching, the system can more efficiently process configuration requests from different business objects, optimize the system's data processing flow, and improve the overall performance of the system.

[0503] Furthermore, based on the system type of the business system, N matching configuration items are displayed to set the notification method. The system type of the business system is divided according to business function, business scope, and geographical scope involved in the business function. By combining the object type of the business object and the system type of the business system to determine the configuration items, from the technical perspective of system architecture and adaptability, the system can analyze and match the needs of business objects from multiple dimensions. This enhances the system's adaptability to complex business scenarios and improves its stability and compatibility in different business environments. At the same time, the multi-dimensional configuration method helps the system allocate resources more rationally, improve resource utilization efficiency, and avoid resource waste caused by improper configuration.

[0504] Furthermore, the first setting operation triggers the setting of the first configuration item to generate sub-configuration information for the first notification method. By receiving parameter information from the first notification identifier field and the first notification content field in the first configuration item and generating sub-configuration information accordingly, the specific process and information source for setting the notification method are clarified from the technical perspective of data processing and information accuracy. This enables the system to accurately obtain and process the configuration information input by business objects, improving the accuracy of notification method settings. At the same time, the standardized configuration process helps the system to effectively manage and store configuration information, facilitating subsequent querying and use, and optimizing the system's data management mechanism.

[0505] Furthermore, the notification method configuration information is updated in response to notification method change events. These events include editing operations on the notification method sub-configuration information by the first business object, changes in the object type of the first business object, and changes in the system type of the business system. In cross-regional business scenarios, this dynamic update mechanism, in terms of system flexibility and adaptability, ensures that the notification method configuration information keeps pace with changes in business objects and business systems. This guarantees consistency between the notification method and the actual business situation, avoids notification failures or inaccuracies caused by information lag, and improves the stability and reliability of the system in dynamic environments.

[0506] Furthermore, the second terminal device displays a message notification management interface for managing notifications within the business system. Responding to a second setting operation, it configures the notification message settings for the business system, including notification scenario configuration and notification template configuration. Then, it sends notification messages to the business objects within the business system according to this configuration. From a system management and information distribution technical perspective, the message notification management interface provides operators with a centralized operating platform, enabling them to uniformly configure and manage the sending of notification messages. This improves operational efficiency and reduces the error rate of manual operations. Simultaneously, by configuring notification scenarios and templates, the system can generate accurate notification messages based on different business scenarios and notification requirements, improving the targeting and effectiveness of notification messages.

[0507] Furthermore, the notification scenario includes notification events, each corresponding to a business function module of the business system. When a business function module is triggered, a notification message needs to be sent to the business object, and the notification message supports multiple notification methods for output. The notification scenario configuration information and notification template configuration information contain detailed descriptive information, such as descriptions of the notification scenario and event, identifiers of the business function module, and identifiers of the notification method. From the technical perspective of system logic and message distribution, this design enables the system to accurately determine notification events based on the triggering status of business function modules and select the appropriate notification method to send notification messages. This improves the accuracy and efficiency of message distribution, avoids unnecessary message sending, and optimizes the system's message distribution logic.

[0508] Furthermore, the batch notification operation in management allows receiving message files containing target message content and batch notification description information, and processing target messages in batches according to the file. From a data processing and efficiency improvement perspective, when business systems experience anomalies or are in special scenarios, batch notification operations can process multiple notification messages at once, reducing the number of system processing steps and the workload of operations personnel. This improves the system's response speed and processing efficiency in emergency situations, enhancing the system's emergency handling capabilities.

[0509] Furthermore, the server obtains notification method configuration information from the first terminal device and notification message configuration information from the second terminal device. Based on these two pieces of information, it encapsulates and processes the first notification message in the business system and sends it to the first terminal device. From a data integration and message processing technical perspective, the server's centralized processing method effectively integrates the notification methods set by the business objects and the notification message information configured by the operators. This ensures the consistency and accuracy of notification messages during encapsulation and transmission, reducing errors in data transmission and processing. Simultaneously, centralized management and processing facilitate unified management of notification messages by the system, improving system maintainability.

[0510] Furthermore, the server determines the M3 notification methods to be used for the first notification message based on the notification method configuration information and the notification message configuration information. This is the intersection of the M1 and M2 notification methods. Then, it encapsulates the first notification message according to the corresponding notification template. From the technical perspective of data filtering and message formatting, determining the notification method by finding the intersection can filter out notification methods that conform to both the business object settings and the operational personnel configurations, improving the accuracy of notification method selection. Encapsulating the message according to the corresponding notification template ensures that the format and content of the notification message meet the preset requirements, improving the standardization and readability of the notification message and optimizing the system's message encapsulation process.

[0511] Furthermore, after encapsulation, M3 first notification messages are obtained, each corresponding one-to-one with one of the M3 notification methods. These are then sent within the first transaction procedure, employing an idempotent control strategy to ensure that only one message is sent to the first terminal device. This idempotent control strategy, by creating a unique index in the notification center's database, guarantees that the notification message is sent only once, avoiding duplicate message transmissions due to repeated requests or operations. This reduces system resource waste, improves the accuracy and reliability of message transmission, and also ensures data consistency, preventing data conflicts and errors.

[0512] Furthermore, the second notification message in the business system, after encapsulation, yields M3 second notification messages corresponding one-to-one with the M3 notification methods. These are then sent in the second transaction procedure, employing a concurrency control strategy to concurrently send the first and second notification messages to the first terminal device. The concurrency control strategy utilizes various mechanisms, including locking, multi-version concurrency control, timestamp sorting, optimistic concurrency control, and pessimistic concurrency control, to ensure data consistency and integrity in multi-business object or multi-task environments from a technical perspective of multi-task processing and data consistency. Concurrent sending of notification messages improves system processing efficiency, reduces message sending latency, enables business objects to obtain notification messages more promptly, and optimizes system performance in multi-task environments.

[0513] Furthermore, the state machine generated during the transmission of the first notification message is obtained. This state machine describes the different states of the message during transmission, including start, processing, success, failure, retry, and retry exceeding limits. This state machine is then sent to the second terminal device. From a system monitoring and troubleshooting perspective, the state machine can monitor the transmission status of notification messages in real time. Operators can promptly understand the transmission status of notification messages based on the information provided by the state machine. In case of anomalies, problems can be quickly located and corresponding measures taken, improving the system's troubleshooting and handling capabilities, and enhancing the system's stability and reliability.

[0514] Furthermore, a domain model is obtained, comprising a notification management model, a notification template information model, and a notification method information model. Each model manages its corresponding configuration information, and the management architecture is constructed using an aggregate design, interacting through an aggregate root identifier. From a system architecture and data management perspective, the domain model design enables effective management and coordination of various business processes within the system. Different models are responsible for different business processes, ensuring the independence and specialization of each process. The aggregate-designed management architecture links the various models, ensuring data consistency and integrity, and improving the overall management efficiency and scalability of the system.

[0515] The specification also mentions that the message processing system provided in this application embodiment is deployed in a blockchain network, with a first terminal device, a second terminal device, and a server acting as node devices to form the blockchain network. From a technical perspective of data security and trustworthiness, the distributed ledger characteristic of the blockchain network ensures the immutability and traceability of data in the message processing flow. During message processing, the recording and transmission of data such as notification method configuration information and notification messages are accurately recorded on the blockchain. Any modification to the data will be detected by other nodes, which improves data security and trustworthiness. At the same time, the blockchain's consensus mechanism ensures data consistency among nodes, avoids data conflicts and errors, and enhances the stability and reliability of the system in data processing and storage.

[0516] In addition, the message notification settings interface can be triggered in several ways, including displaying the service interface of the business system, triggering through the message notification settings entry, detecting preset operations in the operation area, and detecting when a setting prompt message is selected. From a technical perspective of user interaction and system response, multiple triggering methods provide business users with more operational options, improving the convenience of user operation. Different triggering methods can adapt to the operating habits and usage scenarios of different business users, enhancing the user experience of the system. At the same time, the system can respond to these triggering operations in a timely manner, quickly displaying the message notification settings interface, improving the system's response speed and interaction efficiency.

[0517] During the notification setup process, notification content can be prioritized by dragging and dropping message type options to determine priority. From a technical perspective of message processing and resource allocation, prioritization allows the system to sort and process notification messages according to the needs of business users. When resources are limited, the system can prioritize high-priority notification messages, ensuring that important notifications are delivered to business users in a timely manner, thus improving system resource utilization efficiency and the targeted nature of message processing.

[0518] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification. The above embodiments only illustrate several implementation methods of this application, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that for those skilled in the art, several modifications and improvements can be made without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A message processing method, executed by a first terminal device, the method comprising: Display the message notification settings interface, which is used to set the notification method for the business system; In response to the first setting operation, notification method configuration information for the business system is set, wherein the notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer; and When the first notification message is received from the business system, the first notification message is output in one of the M1 configured notification methods.

2. The method as described in claim 1, wherein the first terminal device is a terminal device used by a first business object in the business system; the method further includes: Based on the object type of the first business object, display N configuration items that match the object type of the first business object. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1. The method for classifying the object type of the first business object includes at least one of the following: classifying according to the geographical scope of the first business object, classifying according to the permission level of the first business object in the business system, and classifying according to the business scope operated by the first business object.

3. The method as described in claim 1 or 2, further comprising: Based on the system type of the business system, display N configuration items that match the system type of the business system. Each configuration item is used to set a notification method, where N is a positive integer and N≥M1. The system type classification method of the business system includes at least one of the following: classification according to the business function of the business system, classification according to the business scope of the business system, and classification according to the geographical scope involved in the business function of the business system.

4. The method as described in claim 2 or 3, wherein the first setting operation includes a triggering operation of a first configuration item among the N configuration items, the first configuration item being any one of the N configuration items; the first configuration item is used to set a first notification method; the notification method configuration information includes sub-configuration information of the first notification method; In response to the first setting operation, the notification method configuration information for the business system is set, including: In response to a trigger operation on the first configuration item, the system receives parameter information from the configuration fields of the first configuration item; the configuration fields of the first configuration item include a first notification identifier field and a first notification content field. Based on the parameter information of the configuration fields in the first configuration item, generate sub-configuration information for the first notification method; The first notification identifier field is used to set the notification identifier to which the notification message is output to the business object when the notification message is output according to the first notification method; the first notification content field is used to set the message type of the notification message output according to the first notification method.

5. The method according to any one of claims 1 to 4, wherein the method further comprises: In response to a notification method change event, update the notification method configuration information; The notification method change event includes at least one of the following: the first business object in the business system performs an editing operation on the sub-configuration information of any of the M1 notification methods, the object type of the first business object changes, and the system type of the business system changes; The business system is applied in cross-regional business scenarios, which refer to business execution involving at least two different regions.

6. A message processing method, executed by a second terminal device, the method comprising: The message notification management interface is displayed. The message notification management interface is used to perform notification management operations on the business system. The notification management operations include a second setting operation. In response to the second setting operation, the notification message configuration information of the business system is set; the notification message configuration information includes notification scenario configuration information and notification template configuration information, wherein the notification scenario configuration information is used to indicate the notification scenario in the business system; the notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer; and According to the notification message configuration information of the business system, send notification messages to the business objects in the business system.

7. The method as described in claim 6, wherein the notification scenario includes at least one notification event, each notification event belongs to a business function module in the business system, and whenever any business function module in the business system is triggered to generate a corresponding notification event, a notification message needs to be sent to the business object in the business system; the notification message corresponding to each notification event supports output using at least one notification method; wherein, The notification scenario configuration information includes at least one of the following: description information of the notification scenario, description information of the notification event in the notification scenario, identifier of the business function module corresponding to the notification event, object type of the notified business object, identifier of the M2 notification methods configured for the notification event, number of retries when the notification message is sent, and retry time when the notification message is sent. The notification template configuration information includes at least one of the following: description information of the applicable notification scenario, description information of the applicable notification event, identifier of the applicable business function module, identifier of the applicable notification method, and description information of the notification template; the description information of the notification template includes the identifier of the notification template, the message format of the notification template, and the validity period of use.

8. The method of claim 6 or 7, wherein the management operation further includes a batch notification operation; the method further includes: In response to the batch notification operation, a message file is received; the message file contains the message content of the target message to be batch notified and batch notification description information, the batch notification description information including at least one of the following: the type of business object of the batch notification, the identifier of the notification method used by the batch notification, and the description information of the notification template corresponding to the notification method used by the batch notification; The target messages are batch-notified according to the message file.

9. A message processing method, executed by a server, the method comprising: Obtain notification method configuration information for the business system from the first terminal device. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer. The notification message configuration information of the business system is obtained from the second terminal device. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer. Based on the notification method configuration information and the notification message configuration information, the first notification message in the business system is encapsulated. and The encapsulated first notification message is sent to the first terminal device for output.

10. The method as described in claim 9, wherein encapsulating the first notification message in the business system based on the notification method configuration information and the notification message configuration information includes: Based on the notification method configuration information and the notification message configuration information, M3 notification methods to be used for the first notification message are determined; wherein, the M3 notification methods are the intersection of the M1 notification methods and the M2 notification methods, and M3 is a positive integer; The first notification message is encapsulated according to the notification templates corresponding to the M3 notification methods.

11. The method as described in claim 10, wherein after encapsulation processing, M3 first notification messages are obtained, and the M3 first notification messages correspond one-to-one with the M3 notification methods; the step of sending the encapsulated notification messages to the first terminal device for output includes: The sending operation of the M3 first notification messages is performed in the first transaction procedure; An idempotent control strategy is used to control the sending operation in the first transaction procedure so that one of the M3 first notification messages is sent to the first terminal device for output.

12. The method as described in claim 11, wherein the business system further includes a second notification message, and the second notification message is encapsulated to obtain M3 second notification messages, wherein the M3 second notification messages correspond one-to-one with the M3 notification methods; the method further includes: The sending operation of the M3 second notification messages is performed in the second transaction procedure; The second transaction procedure is a different transaction procedure from the first transaction procedure; A concurrency control strategy is adopted to send the first notification message and the second notification message concurrently to the first terminal device for output.

13. The method of any one of claims 9 to 12, wherein the method further comprises: Obtain the state machine generated during the sending of the first notification message; wherein, the state machine is used to describe the different states corresponding to the first notification message during the sending process; The state machine corresponding to the first notification message is sent to the second terminal device for output. The states described by the state machine include: start state, processing state, successful transmission state, failed transmission state, retry transmission state, and retry limit failure state.

14. The method of any one of claims 9 to 13, wherein the method further comprises: Obtain the domain model, which includes a notification management model, a notification template information model, and a notification method information model; The notification method information model is invoked to manage the notification method configuration information, the notification template information model is invoked to manage the notification message configuration information, and the notification management model is invoked to manage the sending process of the first notification message in the business system. Each of the domain models adopts an aggregate design approach to construct a management architecture. Each of the domain models has its own aggregate root identifier, and each of the domain models interacts with other domain models through the aggregate root identifier during its management process.

15. A message processing apparatus, comprising: The display unit is used to display the message notification setting interface, which is used to set the notification method for the business system. The processing unit is configured to, in response to a first setting operation, set notification method configuration information for the business system, wherein the notification method configuration information indicates M1 notification methods, where M1 is a positive integer; and The output unit is used to output the first notification message in one of the M1 set notification methods when the first notification message is received from the business system.

16. A message processing apparatus, comprising: The display unit is used to display the message notification management interface, which is used to perform notification management operations on the business system. The notification management operations include a second setting operation. The processing unit is configured to, in response to the second setting operation, set the notification message configuration information of the business system; the notification message configuration information includes notification scenario configuration information and notification template configuration information, the notification scenario configuration information is used to indicate the notification scenario in the business system; the notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer; and The sending unit is used to send notification messages to business objects in the business system according to the notification message configuration information of the business system.

17. A message processing apparatus, comprising: The acquisition unit is used to acquire notification method configuration information for the business system from the first terminal device. The notification method configuration information is used to indicate M1 notification methods, where M1 is a positive integer. The acquisition unit is further configured to acquire notification message configuration information of the business system from the second terminal device. The notification message configuration information includes notification scenario configuration information and notification template configuration information. The notification scenario configuration information is used to indicate the notification scenario in the business system. The notification template configuration information is used to indicate M2 notification methods under the notification scenario and the notification template corresponding to each notification method, where M2 is a positive integer. The processing unit is configured to encapsulate and process the first notification message in the business system based on the notification method configuration information and the notification message configuration information. and The sending unit is used to send the encapsulated first notification message to the first terminal device for output.

18. A computer device, comprising: Memory and processor; A memory, wherein one or more computer programs are stored; A processor for loading one or more computer programs to implement the message processing method as described in any one of claims 1-5, 6-8 or 9-14.

19. A computer-readable storage medium storing a computer program adapted to be loaded by a processor and to perform the message processing method as described in any one of claims 1-5, 6-8 or 9-14.

20. A computer program product comprising a computer program adapted to be loaded by a processor and to perform the message processing method as described in any one of claims 1-5, 6-8 or 9-14.

Images