Message generation method and device, electronic equipment and storage medium

Abstract

The application provides a message generation method and device, electronic equipment and storage medium, which can be applied to the financial field or other fields, a standard function interface and a custom interface are used between a requestor system and a service system, the requestor system uniformly provides a custom interface declaration interface for each service system, each service system implements custom interface declaration on the custom interface declaration interface, and the custom interfaces of each service system are independent of each other. Since the loop body can be looped multiple times, the custom field can be theoretically increased infinitely, when the requestor system and the service system communicate, at least one custom field data is assembled into a message according to the loop body format, flexible configuration and unified analysis of the custom interface are realized, and when the service system needs to increase, modify or delete the custom field, the service system can maintain the custom interface declaration interface by itself, and the requestor system does not need to be developed again.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, more particularly, to a message generation method and device, electronic equipment and storage medium. BACKGROUND

[0002] At present, the interaction between various IT systems is more and more, and the scene is more and more complex. With the continuous development of business, the system needs to have the ability to quickly adjust to adapt to the change of business. Especially the unified entrance of all jurisdictions, which links to various local characteristic systems in the background, or interfaces with multiple service providers, which needs to solve the common function and specially process the differentiation of each system, therefore, the interface between systems faces more and more challenges in timeliness, flexibility and complexity.

[0003] At present, the interface between systems needs to define and process fields one by one in advance, and increase the reserved field to reduce the interface change. For the one-to-many situation and the special message needs to be processed, the current method is to process according to the standard message + characteristic message, but the increase of each characteristic message needs to be modified and developed by the service side and the request side at the same time, and the above situation cannot meet the rapid change and definition of the interface. SUMMARY

[0004] Therefore, the present application provides a message generation method and device, electronic equipment and storage medium, which can be maintained by the service side system through the self-defined interface declaration interface when the self-defined field needs to be added, modified or deleted, and the request side system does not need to be developed again.

[0005] In order to achieve the above application purpose, the specific technical scheme provided by the present application is as follows:

[0006] In the first aspect, the present application embodiment provides a message generation method applied to a request side system, the request side system corresponds to at least one service side system, and the method comprises:

[0007] Receiving the self-defined interface declaration sent by the service side system, the self-defined interface declaration is configured by the self-defined interface declaration interface provided by the request side system for each service side system;

[0008] Analyzing the self-defined interface declaration to obtain at least one self-defined field data corresponding to the self-defined interface;

[0009] Assembling the at least one self-defined field data into a message according to the loop body format, and each self-defined field corresponds to a loop body;

[0010] Assemble the message corresponding to the standard function interface and the message corresponding to the custom interface to generate a request message, the standard function interface being a common interface of each service system.

[0011] In some embodiments, the custom interface declaration interface includes a custom message type configuration interface and a custom field configuration interface, the custom field configuration interface including a field type, a field order, a field name, a field length, and an extension attribute.

[0012] In some embodiments, the method further includes:

[0013] receiving a message sent by a service system;

[0014] parsing the received message according to the standard function interface and the custom interface to obtain the message corresponding to the standard function interface and the message corresponding to the custom interface;

[0015] parsing the message corresponding to the custom interface according to a loop body format to obtain custom field data corresponding to each loop body, the custom field data including each attribute of a custom field and a value of each attribute.

[0016] In some embodiments, after obtaining the custom field data corresponding to each loop body, the method further includes:

[0017] verifying the message corresponding to the custom interface according to the custom interface declaration.

[0018] In a second aspect, an embodiment of the present application provides a message generation device applied to a request system, the request system corresponding to at least one service system, and the device including:

[0019] a declaration receiving unit configured to receive a custom interface declaration sent by a service system, the custom interface declaration being configured by a service system through a custom interface declaration interface provided uniformly by the request system for each service system;

[0020] a declaration parsing unit configured to parse the custom interface declaration to obtain at least one custom field data corresponding to the custom interface;

[0021] a first message assembling unit configured to assemble the at least one custom field data into a message according to a loop body format, each custom field corresponding to one loop body;

[0022] a second message assembling unit configured to assemble the message corresponding to the standard function interface and the message corresponding to the custom interface to generate a request message, the standard function interface being a common interface of each service system.

[0023] In some embodiments, the custom interface declaration interface includes a custom message type configuration interface and a custom field configuration interface, and the custom field configuration interface includes a field type, a field order, a field name, a field length, and an extension attribute.

[0024] In some embodiments, the apparatus further includes:

[0025] a message receiving unit configured to receive a message sent by a service system;

[0026] a first message parsing unit configured to parse the received message according to a manner of adding the custom interface to the standard function interface, to obtain a message corresponding to the standard function interface and a message corresponding to the custom interface;

[0027] a second message parsing unit configured to parse the message corresponding to the custom interface according to a loop body format, to obtain custom field data corresponding to each loop body, the custom field data including various attributes of a custom field and values of the various attributes.

[0028] In some embodiments, the apparatus further includes:

[0029] a message checking unit configured to check the message corresponding to the custom interface according to the custom interface declaration.

[0030] In a third aspect, an electronic device is provided, and the electronic device includes a processor and a memory;

[0031] The memory is configured to store program code and transmit the program code to the processor.

[0032] The processor is configured to execute a message generation method according to instructions in the program code.

[0033] In a fourth aspect, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement a message generation method according to any one of the implementation manners of the first aspect.

[0034] Compared with the prior art, the present application has the following advantages:

[0035] The application discloses a message generation method and device, electronic equipment and a storage medium. A standard function interface and a self-defined interface are used between a requestor system and a service system. The standard function interface is a common interface of each service system. The requestor system provides a self-defined interface declaration interface for each service system. Each service system implements self-defined interface declaration in the self-defined interface declaration interface. The self-defined interfaces of each service system are independent of each other. Since the loop body can be looped multiple times, the self-defined field can be theoretically increased infinitely. When the requestor system and the service system communicate, at least one self-defined field data is assembled into a message according to the loop body format, flexible configuration and unified analysis of the self-defined interface are realized, and the service system can maintain the self-defined interface declaration interface when the service system needs to increase, modify or delete the self-defined field, and the requestor system does not need to be developed secondarily. BRIEF DESCRIPTION OF DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description only constitute a part of the embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative labor on the basis of the provided drawings.

[0037] Figure 1 A flowchart of a message generation method disclosed by the embodiment of the present application is shown in the figure.

[0038] Figure 2 A self-defined field data in a self-defined interface declaration disclosed by the embodiment of the present application is shown in the figure.

[0039] Figure 3 A part of a method flowchart of a message generation method disclosed by the embodiment of the present application is shown in the figure.

[0040] Figure 4 A structure diagram of a message generation device disclosed by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0041] The technical solutions in the embodiments of the present application will be clearly and completely described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments only constitute a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the protection scope of the present application.

[0042] The application provides a message generation method and device, electronic equipment and storage medium, which are applied to an inter-system communication scene, a requestor system corresponds to at least one service system, one service system corresponds to at least one requestor system, based on existing various interface message processing mechanisms, not limited to specific implementation technologies, including but not limited to json, xml and the like, as long as a loop body can be processed. A standard function interface and a custom interface are used between the requestor system and the service system, the standard function interface is a common interface of each service system, the requestor system uniformly provides a custom interface declaration interface for each service system, each service system implements custom interface declaration on the custom interface declaration interface, and the custom interfaces of each service system are independent of each other. The requestor system and the service system use a unified message analysis method, that is, a message corresponding to a custom interface is analyzed according to a loop body format, the service system can maintain itself through the custom interface declaration interface when a custom field needs to be added, modified or deleted, and the requestor system does not need to be developed again.

[0043] Please refer to Figure 1 The application discloses a message generation method applied to a requestor system, the requestor system corresponds to at least one service system, and specifically includes the following steps:

[0044] S101: receiving a custom interface declaration sent by a service system, the custom interface declaration being configured by the service system through a custom interface declaration interface uniformly provided by the requestor system for each service system;

[0045] The custom interface declaration interface includes a custom message type configuration interface and a custom field configuration interface.

[0046] The custom message type configuration interface includes a message type, an interface type, whether to be enabled, custom input prompts and the like.

[0047] The custom field configuration interface includes a field type, a field sequence, a field name, a field length, whether to be enabled, whether to be inputted and extension attributes and the like.

[0048] It should be noted that the custom interface declaration interfaces configured by each service system are the same, the field type in the custom field configuration interface is within a field type range agreed in advance by the requestor system and each service system, and it is ensured that the requestor system and each service system can process the custom fields declared by the service system.

[0049] Based on the above custom interface declaration, the attributes of each custom field can be applied, such as a field type, a name, a length, input limitation, input necessity and the like of the field, and whether to limit a total length of a message, a number of fields and a number of loops.

[0050] S102: Analyze the custom interface declaration to obtain at least one custom field data corresponding to the custom interface;

[0051] Figure 2 For the custom field data in the custom interface declaration, the field name includes: field quantity (DEFINE_COUNT), field serial number (DEFINE_NUM), field type (DEFINE_TYPE), field key value (DEFINE_KEY), and field value (DEFINE_VALUE). The field quantity (DEFINE_COUNT) is a required item, indicating the number of loop bodies, that is, the number of custom fields. The field serial number (DEFINE_NUM) indicates the custom field serial number. The field type (DEFINE_TYPE) includes DATE, NUMBER, BOX, TEXT, etc., which is set according to the actual application scenario. The field key value (DEFINE_KEY) indicates the custom field name. The field value (DEFINE_VALUE) indicates the custom field content.

[0052] S103: Assemble the at least one custom field data into a message according to the loop body format, and each custom field corresponds to a loop body;

[0053] Assembling the at least one custom field data into a message according to the loop body format means that the value and attribute of the custom field are assembled as a loop body to display the custom field, and all defined custom fields are integrated into the loop. That is, each custom field is a single loop in the loop body, and each custom field is represented by each single loop of the loop body.

[0054] S104: Assemble the message corresponding to the standard function interface and the message corresponding to the custom interface to generate a request message, and the standard function interface is a common interface for each service system.

[0055] Taking the xml as an example, the following is a reference style of the message corresponding to the standard function interface and the message corresponding to the custom interface:

[0056] <xx>Standard function interface corresponding to the message, slightly< / xx>

[0057] --The following is the message corresponding to the custom interface

[0058] <?xml version=”1.0” encoding=”UTF-8”>

[0059] <msg>

[0060] <DEFINE_COUNT>4< / DEFINE_COUNT> -- define the number of fields to be processed this time, can be increased

[0061] <definelist>-- each loop body, representing a custom field, containing attributes, values

[0062] <DEFINE_NUM>1< / DEFINE_NUM> -- field serial number

[0063] <DEFINE_TYPE>DATE< / DEFINE_TYPE> -- field type

[0064] <DEFINE_KEY>Application date< / DEFINE_KEY> -- field key value

[0065] <DEFINE_VALUE>20211010< / DEFINE_VALUE> -- field value

[0066] < / definelist>

[0067] <definelist>

[0068] <DEFINE_NUM>3< / DEFINE_NUM>

[0069] <DEFINE_TYPE>BOX< / DEFINE_TYPE>

[0070] <DEFINE_KEY>Application Type< / DEFINE_KEY>

[0071] <DEFINE_VALUE>

[0101] Autonomous< / DEFINE_VALUE>

[0072] < / definelist>

[0073] <definelist>

[0074] <DEFINE_NUM> 4< / DEFINE_NUM>

[0075] <DEFINE_TYPE> NUMBER< / DEFINE_TYPE>

[0076] <DEFINE_KEY> Transaction amount< / DEFINE_KEY>

[0077] <DEFINE_VALUE> February 2000< / DEFINE_VALUE>

[0078] < / definelist>

[0079] <definelist>

[0080] <DEFINE_NUM> 5< / DEFINE_NUM>

[0081] <DEFINE_TYPE> TEXT< / DEFINE_TYPE>

[0082] <DEFINE_KEY> Application Opinions< / DEFINE_KEY>

[0083] <DEFINE_VALUE> agree< / DEFINE_VALUE>

[0084] < / definelist>

[0085] ...

[0086] < / msg>

[0087] That is, after the service system completes the custom interface declaration, the request system and the service system both need to process according to the custom interface declaration in the custom interface design loop body, each custom field corresponds to a loop body, and the custom field data is declared in the loop body, including: field serial number, field type, field key value, and field value, that is, the message protocol between the request system and the service system is generated, and the request system and the service system agree on a unified analysis processing method of the loop body. This process only needs the service system to be developed and modified according to the required function, and the request system does not need to be changed, and each custom interface is independent of each other and is not affected by other service systems.

[0088] After the message protocol is generated through the custom interface declaration, inter-system communication can be performed according to the message protocol, and the request system can receive and process the message sent by the service system. Please refer to Figure 2 After the above embodiment S104, the following steps can also be included:

[0089] S201: receiving the message sent by the service system;

[0090] S202: analyzing the received message according to the standard function interface plus custom interface mode to obtain the message corresponding to the standard function interface and the message corresponding to the custom interface;

[0091] S203: analyzing the message corresponding to the custom interface according to the loop body format to obtain the custom field data corresponding to each loop body, and the custom field data includes the attributes of the custom field and the values of the attributes.

[0092] Further, a message checking mechanism between systems can be added, and the message corresponding to the custom interface is checked according to the custom interface declaration, such as legality checking, integrity checking, etc., to ensure that the custom interfaces defined by both parties remain consistent.

[0093] Based on the message generation method disclosed in the above embodiment, the present embodiment discloses a message generation device, which is applied to a request system, and the request system corresponds to at least one service system. Please refer to Figure 4 The device includes:

[0094] The declaration receiving unit 401 is configured to receive the custom interface declaration sent by the service system, and the custom interface declaration is configured by the service system through the custom interface declaration interface provided uniformly by the request system for each service system;

[0095] The declaration analysis unit 402 is configured to analyze the custom interface declaration to obtain at least one custom field data corresponding to the custom interface;

[0096] The first message assembling unit 403 is configured to assemble the at least one custom field data into a message in a loop body format, each custom field corresponding to a loop body.

[0097] The second message assembling unit 404 is configured to assemble a message corresponding to a standard function interface and a message corresponding to the custom interface to generate a request message, the standard function interface being a common interface of each service system.

[0098] In some embodiments, the custom interface declaration interface comprises a custom message type configuration interface and a custom field configuration interface, and the custom field configuration interface comprises a field type, a field sequence, a field name, a field length, and an extension attribute.

[0099] In some embodiments, the apparatus further comprises:

[0100] The message receiving unit is configured to receive a message sent by a service system.

[0101] The first message parsing unit is configured to parse the received message according to a manner of the standard function interface plus the custom interface to obtain a message corresponding to the standard function interface and a message corresponding to the custom interface.

[0102] The second message parsing unit is configured to parse the message corresponding to the custom interface according to the loop body format to obtain custom field data corresponding to each loop body, the custom field data comprising each attribute of a custom field and a value of each attribute.

[0103] In some embodiments, the apparatus further comprises:

[0104] The message checking unit is configured to check the message corresponding to the custom interface according to the custom interface declaration.

[0105] The message generating apparatus disclosed in the embodiments adopts a standard function interface plus a custom interface between a request system and a service system, the standard function interface being a common interface of each service system, the request system providing a custom interface declaration interface for each service system, each service system implementing a custom interface declaration in the custom interface declaration interface, and the custom interfaces of each service system being independent of each other. Since a loop body can be looped multiple times and a custom field can be theoretically increased infinitely, the request system and the service system communicate by assembling at least one custom field data into a message in a loop body format, realizing flexible configuration and unified parsing of the custom interface, and the service system can maintain the custom interface declaration interface by itself when it needs to increase, modify, or delete a custom field, without the need of secondary development of the request system.

[0106] The embodiment of the present application also provides an electronic device, which comprises a processor and a memory;

[0107] The memory is used for storing program codes and transmitting the program codes to the processor;

[0108] The processor is used for executing the following packet generation method according to instructions in the program codes:

[0109] receiving a custom interface declaration sent by a service system, wherein the custom interface declaration is configured by the service system through a custom interface declaration interface provided uniformly by the request system for each service system;

[0110] parsing the custom interface declaration to obtain at least one custom field data corresponding to the custom interface;

[0111] assembling the at least one custom field data into a packet in a loop body format, and each custom field corresponds to a loop body;

[0112] assembling a packet corresponding to a standard function interface and a packet corresponding to the custom interface to generate a request packet, wherein the standard function interface is a common interface of each service system.

[0113] Further, the custom interface declaration interface comprises a custom packet type configuration interface and a custom field configuration interface, and the custom field configuration interface comprises a field type, a field sequence, a field name, a field length and an extension attribute.

[0114] Further, the method further comprises:

[0115] receiving a packet sent by a service system;

[0116] parsing the received packet according to a mode of the standard function interface and the custom interface to obtain a packet corresponding to the standard function interface and a packet corresponding to the custom interface;

[0117] parsing the packet corresponding to the custom interface in a loop body format to obtain custom field data corresponding to each loop body, wherein the custom field data comprises each attribute of a custom field and a value of each attribute.

[0118] Further, after obtaining the custom field data corresponding to each loop body, the method further comprises:

[0119] verifying the packet corresponding to the custom interface according to the custom interface declaration.

[0120] The embodiment of the present application also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is executed by a processor to realize the following message generation method.

[0121] receiving a custom interface declaration sent by the service system, wherein the custom interface declaration is configured by the service system through a custom interface declaration interface provided by the request system for each service system;

[0122] analyzing the custom interface declaration to obtain at least one custom field data corresponding to the custom interface;

[0123] assembling the at least one custom field data into a message in a loop body format, wherein each custom field corresponds to a loop body, and the loop body contains each attribute and value of the field definition;

[0124] assembling the message corresponding to the standard function interface and the message corresponding to the custom interface to generate a request message, wherein the standard function interface is a common interface of each service system.

[0125] Further, the custom interface declaration interface comprises a custom message type configuration interface and a custom field configuration interface, and the custom field configuration interface comprises a field type, a field sequence, a field name, a field length and an extension attribute.

[0126] Further, the method further comprises:

[0127] receiving a message sent by the service system;

[0128] analyzing the received message according to the standard function interface and the custom interface to obtain the message corresponding to the standard function interface and the message corresponding to the custom interface;

[0129] analyzing the message corresponding to the custom interface according to the loop body format to obtain custom field data corresponding to each loop body, wherein the custom field data comprises each attribute of the custom field and the value of each attribute.

[0130] Further, after obtaining the custom field data corresponding to each loop body, the method further comprises:

[0131] verifying the message corresponding to the custom interface according to the custom interface declaration.

[0132] It should be noted that the message generation method, device, electronic equipment and storage medium provided by the present application can be applied to the financial field or other fields, for example, can be applied to the inter-system communication application scenario in the financial field. Other fields are any field other than the financial field, for example, the power field. The above are only examples and do not limit the application field of the message generation method, device, electronic equipment and storage medium provided by the present application.

[0133] The embodiments in the specification are described in a progressive manner, and each embodiment focuses on the difference from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed by the embodiments, since it corresponds to the method disclosed by the embodiments, the description is relatively simple, and the related parts can be referred to the method part.

[0134] It should be noted that in this paper, relationship terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between the entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or equipment. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or equipment including the element.

[0135] The steps of the method or algorithm described in combination with the embodiments disclosed herein can be implemented directly by hardware, software module executed by a processor, or a combination of the two. The software module can be placed in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, register, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0136] The above-described various embodiments can be combined arbitrarily, and the above-described description of the disclosed embodiments can be replaced or combined with the features described in each embodiment in the specification, so that those skilled in the art can realize or use the present application.

[0137] The foregoing description of the disclosed embodiments enables a person skilled in the art to make or use the application. Modifications of these embodiments will occur to persons of skill in the art, and that the appended claims are intended to cover all such modifications that do not depart from the true spirit and scope of the application. Therefore, the application is not limited to the embodiments shown but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of generating a packet, characterized by, The method is applied to a requestor system corresponding to at least one service provider system, and comprises the following steps: receiving a custom interface declaration sent by the service provider system, the custom interface declaration being completed by the service provider system through a custom interface declaration interface provided uniformly by the requestor system for each service provider system; wherein the service provider system maintains custom fields through the custom interface declaration interface, and the requestor system does not need to be developed secondarily; parsing the custom interface declaration to obtain at least one custom field data corresponding to the custom interface; assembling the at least one custom field data into a message in a loop body format, each custom field corresponding to a loop body; and declaring the custom field data in the loop body; assembling a message corresponding to a standard function interface and a message corresponding to the custom interface to generate a request message, the standard function interface being a common interface of each service provider system.

2. The method of claim 1, wherein, The custom interface declaration interface comprises a custom message type configuration interface and a custom field configuration interface, and the custom field configuration interface comprises a field type, a field order, a field name, a field length and an extension attribute.

3. The method of claim 1, wherein, The method further comprises the following steps: receiving a message sent by the service provider system; parsing the received message according to the standard function interface and the custom interface to obtain a message corresponding to the standard function interface and a message corresponding to the custom interface; parsing the message corresponding to the custom interface in a loop body format to obtain custom field data corresponding to each loop body, the custom field data comprising each attribute of the custom field and the value of each attribute.

4. The method of claim 3, wherein, After obtaining the custom field data corresponding to each loop body, the method further comprises the following steps: verifying the message corresponding to the custom interface according to the custom interface declaration.

5. A packet generating apparatus characterized by comprising: The device is applied to a requestor system corresponding to at least one service provider system, and comprises the following steps: a declaration receiving unit configured to receive a custom interface declaration sent by the service provider system, the custom interface declaration being completed by the service provider system through a custom interface declaration interface provided uniformly by the requestor system for each service provider system; wherein the service provider system maintains custom fields through the custom interface declaration interface, and the requestor system does not need to be developed secondarily; a declaration parsing unit configured to parse the custom interface declaration to obtain at least one custom field data corresponding to the custom interface; a first message assembling unit configured to assemble the at least one custom field data into a message in a loop body format, each custom field corresponding to a loop body; and declare the custom field data in the loop body; a second message assembling unit configured to assemble a message corresponding to a standard function interface and a message corresponding to the custom interface to generate a request message, the standard function interface being a common interface of each service provider system.

6. The apparatus of claim 5, wherein, The self-defined interface declaration interface includes a self-defined message type configuration interface and a self-defined field configuration interface, and the self-defined field configuration interface includes a field type, a field sequence, a field name, a field length, and an extension attribute.

7. The apparatus of claim 5, wherein, The device further includes: a message receiving unit configured to receive a message sent by a service system; a first message analyzing unit configured to analyze the received message according to the standard function interface plus the self-defined interface to obtain a message corresponding to the standard function interface and a message corresponding to the self-defined interface; a second message analyzing unit configured to analyze the message corresponding to the self-defined interface according to a loop body format to obtain self-defined field data corresponding to each loop body, the self-defined field data including various attributes of the self-defined field and values of the various attributes.

8. The apparatus of claim 7, wherein, The device further includes: a message checking unit configured to check the message corresponding to the self-defined interface according to the self-defined interface declaration.

9. An electronic device, comprising: The electronic device includes a processor and a memory; The memory is configured to store program code and transmit the program code to the processor; The processor is configured to execute a message generation method according to instructions in the program code.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the message generation method. The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the message generation method.

Images