Packet sending method and related device

Abstract

The present disclosure provides a message sending method and related equipment, the method comprises the following steps: obtaining message interface specification data, and modifying the code in the code template according to the message interface specification data to obtain message code, wherein the message code is used for checking the message; generating a reporting application according to the message code and a preset reporting code, wherein the reporting code is used for reporting the message; obtaining message data, and generating a target message based on the reporting application and the message data; and sending the target message to a target terminal. In the present disclosure, the message code for checking the message is obtained through the interface report specification data, so that the reporting application is automatically generated through the message code and the reporting code for reporting the message, without manual coding of the reporting application, thereby reducing the generation time of the reporting application and improving the reporting efficiency of the message.

Description

Technical Field

[0001] This disclosure relates to message technology, and more particularly to a message transmission method and related equipment. Background Technology

[0002] In recent years, the rapid development of financial business has placed higher demands on financial risk supervision. Financial institutions submit financial-related data to regulatory authorities in the form of messages for financial risk monitoring.

[0003] Financial institutions have a wide range of financial transactions, resulting in a diverse range of message data. Furthermore, with increased regulatory scrutiny, more and more regulatory bodies are involved in the supervision of financial risks. Different regulatory bodies have different message formats, and given the variety of message data types, it is necessary to configure a wide range of message reporting applications to send the message data to the regulatory bodies.

[0004] In the exemplary technology, the code for the reporting application needs to be coded manually. Since there are many types of reporting applications, a lot of time is required to code the reporting applications, resulting in low message reporting efficiency. Summary of the Invention

[0005] This disclosure provides a message transmission method and related equipment to solve the problem of low message transmission efficiency.

[0006] On the one hand, this disclosure provides a message transmission method, including:

[0007] Obtain message interface specification data, and modify the code in the code template according to the message interface specification data to obtain message code;

[0008] A reporting application is generated based on the message code and the preset reporting code;

[0009] Acquire message data and generate a target message based on the reporting application and the message data;

[0010] The target message is sent to the target terminal.

[0011] In one embodiment, the step of modifying the code in the code template according to the message interface specification data to obtain the message code includes:

[0012] Obtain each first code according to the message interface specification data;

[0013] Determine the first position of each of the first codes in the code template;

[0014] The message code is obtained by replacing the second code at the first position with the first code corresponding to the first position.

[0015] In one embodiment, before the step of determining the first position of each of the first codes in the code template, the method further includes:

[0016] Identify the various first functions required during message transmission, and determine the common target function among these first functions;

[0017] Obtain the third code corresponding to the target function and obtain the fourth code corresponding to the second function, where the second function is the first function that was not identified as the target function;

[0018] Code templates are generated based on each of the third codes and each of the fourth codes, wherein the third codes in the code templates cannot be replaced.

[0019] In one embodiment, the step of generating a reporting application based on the message code and a preset reporting code includes:

[0020] Determine the second position of the message code in the preset first directory, and determine the third position of the preset reporting code in the first directory;

[0021] Add the message code to the second position in the first directory and add the reporting code to the third position in the first directory to obtain the second directory;

[0022] The reporting application is generated based on the second directory.

[0023] In one embodiment, the step of generating a target message based on the reporting application and the message data includes:

[0024] The reporting application verifies the message data;

[0025] After the message data passes verification, the message data is assembled into a target message based on the reporting application.

[0026] In one embodiment, the message code is used to provide a first preset function, and the reporting code is used to provide a second preset function. The first preset function includes a data acquisition function, a data specification verification function, a data addition, deletion, modification, and query function, and a message assembly function. The second preset function includes a message data entry function, a message data verification function, a message receiving function, and a message sending function.

[0027] On the other hand, this disclosure also provides a message transmitting apparatus, including:

[0028] The acquisition module is used to acquire message interface specification data and modify the code in the code template according to the message interface specification data to obtain message code;

[0029] The generation module is used to generate a reporting application based on the message code and a preset reporting code;

[0030] The acquisition module is also used to acquire message data and generate a target message based on the reporting application and the message data;

[0031] The sending module is used to send the target message to the target terminal.

[0032] On the other hand, this disclosure also provides a message sending device, including: a memory and a processor;

[0033] The memory stores computer-executed instructions;

[0034] The processor executes computer execution instructions stored in the memory, causing the processor to perform the message sending method as described above.

[0035] On the other hand, this disclosure also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the message sending method described above.

[0036] On the other hand, this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the message sending method as described above.

[0037] The message sending method and related equipment disclosed herein acquire message interface specification data, modify the code in the code template according to the message interface specification data to obtain message code, generate a reporting application based on the message code and a preset reporting code, generate a target message based on the reporting application and message data, and then send the target message to the target terminal. In this disclosure, the message code used for message verification is obtained through the interface message specification data, and the reporting application is automatically generated using the message code and the reporting code used for message reporting, eliminating the need for manual coding of the reporting application, reducing the generation time of the reporting application, and improving the message reporting efficiency. Attached Figure Description

[0038] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0039] Figure 1 This is a flowchart illustrating the first embodiment of the message sending method disclosed herein;

[0040] Figure 2 This is a schematic diagram of a scenario involving the message sending method disclosed herein;

[0041] Figure 3This is a simplified flowchart illustrating the message sending method disclosed herein;

[0042] Figure 4 This is a flowchart illustrating the second embodiment of the message sending method disclosed herein;

[0043] Figure 5 This is a flowchart illustrating the third embodiment of the message sending method disclosed herein;

[0044] Figure 6 This is a flowchart illustrating the fourth embodiment of the message transmission method disclosed herein;

[0045] Figure 7 This is a schematic diagram of the module of the message sending device disclosed herein;

[0046] Figure 8 This is a schematic diagram of the hardware structure of the device that sends the message in this publication.

[0047] The accompanying drawings have illustrated specific embodiments of this disclosure, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this disclosure to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0048] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0049] In recent years, the rapid development of financial business has placed higher demands on financial risk supervision. Financial institutions submit financial-related data to regulatory authorities in the form of messages for financial risk monitoring.

[0050] Financial institutions have a wide range of financial transactions, resulting in a diverse range of message data. Furthermore, with increased regulatory scrutiny, more and more regulatory bodies are involved in the supervision of financial risks. Different regulatory bodies have different message formats, and given the variety of message data types, it is necessary to configure a wide range of message reporting applications to send the message data to the regulatory bodies.

[0051] The inventors of this disclosure discovered that the code for reporting applications needs to be manually coded. Since there are many types of reporting applications, coding them consumes a significant amount of time, resulting in low message reporting efficiency. Therefore, the inventors conceived of obtaining message code for message verification through interface message specification data. This allows for the automatic generation of reporting applications using the message code and the reporting code used for message reporting, eliminating the need for manual coding, reducing the time required to generate reporting applications, and improving message reporting efficiency.

[0052] The following detailed description, using specific embodiments, illustrates how the technical solutions of this disclosure and this application solve the aforementioned technical problems. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this disclosure will now be described with reference to the accompanying drawings.

[0053] Reference Figure 1 , Figure 1 This is a first embodiment of the message transmission method disclosed herein, which includes the following steps:

[0054] Step S101: Obtain message interface specification data, and modify the code in the code template according to the message interface specification data to obtain message code. The message code is used to verify the message.

[0055] In this embodiment, the executing entity is a message sending device. For ease of description, the term "device" will be used to refer to the message sending device below. A device is any device with data processing capabilities; for example, a device can be a computer.

[0056] Various message data share similarities, and different regulatory authorities also exhibit similar regulatory approaches to these messages.

[0057] For example, different regulatory authorities may require message data to meet established data specifications. Based on the similarity between various message data, common codes are determined for all message data. Furthermore, based on the similarity of regulatory oversight across different regulatory authorities, common codes for submission by each regulatory authority are determined. In addition, for some routine data in the messages, replaceable codes are written for this routine data. A message template is then generated based on these common codes and replaceable codes. It is understandable that the message template contains code that does not need to be replaced; this type of code is considered common code. The message template also contains replaceable code.

[0058] Before sending a message, the device first obtains the message interface specification data. For example, referring to Table-1, the message interface specification data includes the message name, message identifier, message code, and message data definition. The message data definition includes identifiers, data item names, types, lengths, key values, and validation rules. Identifiers include AccountNo, Currency, Balance, BalanceCode, SubmitDate, TotalCount, and AccOrgCode, and also include the corresponding type, length, and validation rules. The validation rules support length, date, non-empty, and regular expression validation for data items.

[0059]

[0060] The message interface specification data can be filled in through a form, a program, or a web page; that is, the device obtains the input message interface specification data. It should be noted that the above is merely an example to illustrate message interface specification data and does not limit the content of the message interface specification data.

[0061] The device modifies the code in the code template based on the message interface specification data to obtain the message code used for message verification. For example, the device generates the code corresponding to the identifier based on the message interface specification, and then replaces the code representing the identifier in the code template with the code corresponding to the identifier in the message interface specification to obtain the modified code template. The various codes in the modified code template constitute the message code.

[0062] Step S102: Generate a reporting application based on the message code and the preset reporting code. The reporting code is used to report the message.

[0063] The message reporting process is fixed, so corresponding code can be generated for the reporting process. This code is defined as the reporting code, which is used to report messages. The device integrates the message code and the reporting code to obtain the reporting application.

[0064] It should be noted that the message code is used to provide the first preset function, and the reporting code is used to provide the second preset function. The first preset function includes data acquisition, data specification verification, data addition, deletion, modification, and query functions, and message assembly. The second preset function includes message data entry, message data review, message reception, and message transmission. The data acquisition function is used to acquire data; the data specification verification function is used to verify the data specifications of the message data; the data addition, deletion, modification, and query functions are used to add, delete, modify, and test the message data; the message assembly function is used to assemble the message data to obtain a message. The message data entry function is used to enter and submit the message data to the application; the message data review function is used to review the message data; the message reception function is used to receive feedback results sent by external devices; and the message transmission function is used to send the message to external devices.

[0065] Reference Figure 2 The message code consists of multiple message data management units. Each message data management unit has data acquisition, data specification verification, data CRUD (Create, Read, Update, Delete) and message assembly functions, and each message data management unit corresponds to the processing of one type of message data. The code corresponding to the message data management unit includes SQL table creation statements, verification rule codes, message data management codes, and user interface codes, etc. For example, the corresponding code types are shown in Table-2.

[0066]

[0067] It should be noted that the code types mentioned above are merely illustrative examples of the codes corresponding to the message data management unit, and do not limit the type of code for the message data management unit.

[0068] Reference Figure 2 as well as Figure 3 The reporting code corresponds to the reporting management module, which includes functions such as reporting process management, message sending, and message receiving. Reporting process management includes message data entry and verification. Report entry is triggered after message data is acquired. In this stage, business personnel need to verify the message data and can modify it according to the actual situation. After successful entry, the verification stage begins. In this stage, business personnel need to verify the message data again. If the verification fails, the message data is returned to the entry stage for further processing. After successful verification, the message sending stage begins. This stage first verifies whether the message data conforms to the specifications. If it does, the message assembly function is called to generate an XML message, which is then sent to the terminal associated with the regulatory agency. After successful message sending, the message receiving stage begins. This stage processes the feedback from the terminal. If the feedback is successful, the reporting process ends; otherwise, the message is returned to the entry stage for further processing.

[0069] Step S103: Obtain message data and generate target message based on the reporting application and message data.

[0070] After obtaining the reporting application, configure the corresponding data source for the reporting application, that is, obtain the message data from the data source, and generate the target message through the reporting application and the message data.

[0071] Specifically, the message data is entered and reviewed. The reporting management module in the reporting application will call the functions of the message data management unit as needed. For example, the data entry and review stages will call the data specification verification function and the message data CRUD function, while the message sending stage will call the data specification verification function and the message assembly function. In this way, the target message can be obtained.

[0072] Furthermore, the device verifies the message data based on the reporting application, and after the message data passes verification, it assembles the message data based on the reporting application to obtain the target message. The message data is verified by the data specification verification function, and the message data is assembled by the message assembly function.

[0073] Step S104: Send the target message to the target terminal.

[0074] After receiving the target message, the device sends the target message to the target terminal, which is the terminal associated with the regulatory authority.

[0075] In this embodiment, message interface specification data is obtained, and the code in the code template is modified according to the message interface specification data to obtain message code. A reporting application is then generated based on the message code and a preset reporting code. Finally, a target message is generated based on the reporting application and message data, and the target message is sent to the target terminal. In this embodiment, message code for verifying messages is obtained through interface message specification data. The reporting application is then automatically generated using the message code and the reporting code used for message reporting, eliminating the need for manual coding of the reporting application, reducing the generation time of the reporting application, and improving the message reporting efficiency.

[0076] Reference Figure 4 The figure shows a second embodiment of the message sending method of this disclosure. Based on the first embodiment, step S102 includes:

[0077] Step S401: Obtain each first code according to the message interface specification data.

[0078] Step S402: Determine the first position of each first code in the code template.

[0079] In this embodiment, the message template includes fixed content and replaceable content, with the fixed content being non-replaceable code. The code template marks the location and code type of the replaceable content.

[0080] After obtaining the message interface specification data, the device parses the message interface specification data and generates multiple first codes. For example, referring to 2, the device generates a first code corresponding to each identifier. The device determines the type of each first code and finds a position in the code template that matches the type of the first code; this position is the first position in the code template where the first code replaces the first code.

[0081] Step S403: Replace the second code at the first position with the first code corresponding to the first position to obtain the message code.

[0082] After determining the first position, the device replaces the second code of the first position with the first code corresponding to the first position, thereby obtaining the message code.

[0083] In this embodiment, the device obtains each first code according to the message interface specification data and determines the first position of each first code in the code template, thereby replacing the second code at the first position with the first code to obtain the message code required by the user.

[0084] Reference Figure 5 , Figure 5 This is a third embodiment of the message transmission method of this disclosure. Based on the second embodiment, before step S402, it further includes:

[0085] Step S501: Determine the various first functions required during message transmission, and determine the common target function among the various first functions.

[0086] In this embodiment, the message template contains both irreplaceable and replaceable code. The irreplaceable code represents common functions during message transmission. For example, before message data is sent to the regulatory authority, it needs to undergo data specification verification, making data specification verification a common function; message data verification requires modification, thus making data addition, deletion, modification, and query functions common functions; furthermore, message data needs to be acquired and assembled into a message, making data acquisition and message assembly functions also common functions.

[0087] To this end, the device determines the various primary functions required during message transmission and identifies common target functions within each primary function. Target functions include, for example, data specification verification, data CRUD operations, data acquisition, and message assembly.

[0088] Step S502: Obtain the third code corresponding to the target function and obtain the fourth code corresponding to the second function, where the second function is the first function that was not identified as the target function.

[0089] The device stores a code corresponding to each function. After determining each target function, the device obtains a third code corresponding to each target function. The device then obtains a fourth code corresponding to the second function. The second function is the first function that was not determined to be a target function.

[0090] Step S503: Generate a code template based on each third code and each fourth code. The third code in the code template cannot be replaced.

[0091] After obtaining the various third and fourth codes, a code template can be generated based on them. If the function corresponding to a third code is a general function, then that third code cannot be replaced.

[0092] In this embodiment, the device generates code templates based on common and non-common functions, thereby facilitating the device to generate the message code required by the user based on the message interface specification data and the code templates.

[0093] Reference Figure 6 , Figure 6 In the fourth embodiment of the message transmission method of this disclosure, based on any one of the first to third embodiments, step S102 includes:

[0094] Step S601: Determine the second position of the message code in the preset first directory, and determine the third position of the preset reporting code in the first directory.

[0095] Step S602: Add message code to the second position of the first directory and report code to the third position of the first directory to obtain the second directory.

[0096] Step S603: Generate a reporting application based on the second directory.

[0097] In this embodiment, the device includes a generation directory, defined as the first directory. The first directory has multiple code entry locations, which are used to add corresponding code.

[0098] After determining the message code, the device determines the second position of the message code in the first target, and determines the third position of the preset reporting code in the first directory.

[0099] The device adds message codes to the second location and reporting codes to the third location to obtain a directory filled with codes, which is defined as the second directory. The device can then generate a reporting application based on the codes added to the second directory.

[0100] In this embodiment, the device integrates message codes and reporting codes through a preset directory to generate the reporting application required for reporting message data.

[0101] This disclosure also provides a message transmitting apparatus, referring to... Figure 7 The message sending device 700 includes:

[0102] The acquisition module 710 is used to acquire message interface specification data and modify the code in the code template according to the message interface specification data to obtain message code. The message code is used to verify the message.

[0103] The generation module 720 is used to generate a reporting application based on the message code and a preset reporting code. The reporting code is used to report the message.

[0104] The acquisition module 710 is used to acquire message data and generate a target message based on the reporting application and the message data;

[0105] The sending module 730 is used to send the target message to the target terminal.

[0106] In one embodiment, the message sending device 700 includes:

[0107] The acquisition module 710 is used to obtain each first code according to the message interface specification data;

[0108] The determination module is used to determine the first position of each piece of code in the code template;

[0109] The replacement module is used to replace the second code at the first position with the first code corresponding to the first position to obtain the message code.

[0110] In one embodiment, the message sending device 700 includes:

[0111] The determination module is used to determine the various first functions required during message transmission, and to determine the common target function among the various first functions;

[0112] The acquisition module 710 is used to acquire the third code corresponding to the target function and the fourth code corresponding to the second function, where the second function is the first function that has not been identified as the target function.

[0113] The generation module 720 is used to generate code templates based on each third code and each fourth code. The third code in the code template cannot be replaced.

[0114] In one embodiment, the message sending device 700 includes:

[0115] The determination module is used to determine the second position of the message code in the preset first directory and the third position of the preset reporting code in the first directory;

[0116] Add a module to add message code in the second position of the first directory and report code in the third position of the first directory to obtain the second directory;

[0117] The generation module 720 is used to generate a reporting application based on the second directory.

[0118] In one embodiment, the message sending device 700 includes:

[0119] The verification function is used to verify message data based on the reporting application;

[0120] The assembly module is used to assemble the message data into the target message based on the sending application after the message data has passed verification.

[0121] In one embodiment, the message code is used to provide a first preset function, and the reporting code is used to provide a second preset function. The first preset function includes data acquisition function, data specification verification function, data addition, deletion, modification and query function, and message assembly function. The second preset function includes message data entry function, message data verification function, message receiving function, and message sending function.

[0122] Figure 8 This is a hardware structure diagram of a message sending device according to an exemplary embodiment.

[0123] The message sending device 800 may include: a processor 801, such as a CPU, a memory 802, and a transceiver 803. Those skilled in the art will understand that... Figure 8 The structure shown does not constitute a limitation on the message transmitting device and may include more or fewer components than illustrated, or combine certain components, or have different component arrangements. Memory 802 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0124] The processor 801 can call the computer program stored in the memory 802 to complete all or part of the steps of the above-described message sending method.

[0125] The transceiver 803 is used to receive information sent by external devices and to send information to external devices.

[0126] A non-transitory computer-readable storage medium, wherein when the instructions in the storage medium are executed by the processor of a message sending device, the message sending device is able to perform the aforementioned message sending method.

[0127] A computer program product includes a computer program that, when executed by a processor of a message sending device, enables the message sending device to perform the message sending method described above.

[0128] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0129] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A message sending method, characterized in that, include: Obtain message interface specification data, and modify the code in the code template according to the message interface specification data to obtain message code, which is used to verify the message; A reporting application is generated based on the message code and a preset reporting code, wherein the reporting code is used to report the message; Acquire message data and generate a target message based on the reporting application and the message data; Send the target message to the target terminal; The step of modifying the code in the code template according to the message interface specification data to obtain the message code includes: Obtain each first code according to the message interface specification data; Determine the first position of each of the first codes in the code template; Replace the second code at the first position with the first code corresponding to the first position to obtain the message code; The step of generating a reporting application based on the message code and a preset reporting code includes: Determine the second position of the message code in the preset first directory, and determine the third position of the preset reporting code in the first directory; Add the message code to the second position in the first directory and add the reporting code to the third position in the first directory to obtain the second directory; The reporting application is generated based on the second directory.

2. The message sending method according to claim 1, characterized in that, Before the step of determining the first position of each of the first codes in the code template, the method further includes: Identify the various first functions required during message transmission, and determine the common target function among these first functions; Obtain the third code corresponding to the target function and obtain the fourth code corresponding to the second function, where the second function is the first function that was not identified as the target function; Code templates are generated based on each of the third codes and each of the fourth codes, wherein the third codes in the code templates cannot be replaced.

3. The message sending method according to claim 1, characterized in that, The step of generating the target message based on the reporting application and the message data includes: The reporting application verifies the message data; After the message data passes verification, the message data is assembled into a target message based on the reporting application.

4. The message transmission method according to any one of claims 1-3, characterized in that, The message code is used to provide a first preset function, and the reporting code is used to provide a second preset function. The first preset function includes data acquisition function, data standard verification function, data addition, deletion, modification and query function, and message assembly function. The second preset function includes message data entry function, message data verification function, message receiving function, and message sending function.

5. A message sending device, characterized in that, include: The acquisition module is used to acquire message interface specification data and modify the code in the code template according to the message interface specification data to obtain message code; The generation module is used to generate a reporting application based on the message code and a preset reporting code; The acquisition module is also used to acquire message data and generate a target message based on the reporting application and the message data; The sending module is used to send the target message to the target terminal; The acquisition module is further configured to acquire each first code according to the message interface specification data; determine the first position of each first code in the code template; replace the second code at the first position with the first code corresponding to the first position to obtain the message code; The generation module is further configured to determine the second position of the message code in a preset first directory, and determine the third position of the preset reporting code in the first directory; add the message code to the second position of the first directory and add the reporting code to the third position of the first directory to obtain the second directory; The reporting application is generated based on the second directory.

6. A message sending device, characterized in that, include: Memory and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the message transmission method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the message transmission method according to any one of claims 1 to 4.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the message sending method according to any one of claims 1 to 4.

Images