Message data information processing method and device, equipment and storage medium

Abstract

The application provides a message data information processing method and device, equipment and a storage medium, and relates to the technical field of data information processing. The method receives message data information and stores the message data information in a message database; in response to a check request message of a preset frequency, the message data information is retrieved from a preset interface topic, the message data information is analyzed to obtain primary key information; according to the primary key information, service data information associated with the primary key information is retrieved from a service database, and the message data information is retrieved from the message database; according to the relationship between the service data information and the message data information, a processing result is determined, and the message data information is processed according to the processing result. By using the technical scheme, an accurate data check mechanism can be realized without increasing additional business pressure.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data information processing, and particularly relates to a message data information processing method and device, equipment and a storage medium. BACKGROUND

[0002] Information systems are often complex, and each information system interacts through an interface. The information system internally persists and saves the interactive information to a database.

[0003] In a specific business scenario, for example, in a high-concurrency or must-be-insured scenario, the interface needs to be processed after responding, that is, the interface interacts in an asynchronous manner, that is, the calling party is informed of the processing success before the actual processing. In this scenario, the response result of the interface and the final database storage are inconsistent, for example, the interface returns a save success, but actually, the information is not saved to the database, which leads to the fact that the operation is not actually executed, but the user receives the feedback message of the data save success.

[0004] Therefore, a message data information processing method is needed, which can realize an accurate data checking mechanism without increasing additional business pressure. SUMMARY

[0005] The present application provides a message data information processing method, which can realize an accurate data checking mechanism without increasing additional business pressure.

[0006] In a first aspect, the present application provides a message data information processing method, which comprises the following steps:

[0007] receiving message data information and storing the message data information in a message database; wherein the message data information is generated by a business system according to a user request message and is sent to a checking system after being generated; the user request message is sent by a user terminal to the business system; and a feedback message corresponding to the user request message is generated by the business system after receiving the user request message and is fed back to the user terminal;

[0008] in response to a preset frequency of a checking request message, the message data information is obtained from a preset interface topic, and the message data information is parsed to obtain primary key information; wherein the preset interface topic is located in a first message middleware; and the first message middleware is used to store the message data information;

[0009] According to the primary key information, service data information associated with the primary key information is retrieved from a service database, and the message data information is retrieved from the message database; wherein the service data information is obtained by analyzing the user request message to obtain original message data information carried in the user request message after the feedback message is sent by the service system, and is obtained by storing the original message data information;

[0010] According to the relationship between the service data information and the message data information, a processing result is determined, and the message data information is processed according to the processing result.

[0011] In one example, the determining of the processing result according to the relationship between the service data information and the message data information comprises:

[0012] If the service data information exists in the service database and is consistent with the message data information, the processing result is determined to be passed.

[0013] If the service data information exists in the service database and is inconsistent with the message data information, the processing result is determined to be not passed.

[0014] If the service data information does not exist in the service database, and the message data information exists in the message database, the processing result is determined according to the message data information.

[0015] If the service data information does not exist in the service database, and the message data information does not exist in the message database, the processing result is determined to be not passed.

[0016] In one example, the determining of the processing result according to the message data information comprises:

[0017] Obtaining a data operation type in the message data information.

[0018] If the data operation type is a preset type, the processing result is determined to be passed.

[0019] If the data operation type is not the preset type, the processing result is determined to be not passed.

[0020] In one example, the processing of the message data information according to the processing result comprises:

[0021] If the processing result is passed, the next message data information is processed.

[0022] If the processing result is not passed, an alarm prompt message is sent to the user.

[0023] In one example, receiving message data and storing the message data in a message database includes:

[0024] Receive the message data information and store the message data information under the interface interaction message topic in the second message middleware;

[0025] The message data information is sent to the message database through the second message middleware.

[0026] In one example, before retrieving the message data information from a preset interface topic in response to a verification request message at a preset frequency, the method further includes:

[0027] The message data information in the second message middleware is stored under a preset interface topic in the first message middleware according to the data operation type.

[0028] In one example, the data operation type includes at least one of the following: add, delete, modify, and query.

[0029] Secondly, this application provides a message data information processing apparatus, the apparatus comprising:

[0030] A receiving unit is configured to receive message data information and store the message data information in a message database; wherein the message data information is generated by the business system based on a user request message and sent to the verification system after generation; the user request message is sent from the user terminal to the business system; the feedback message corresponding to the user request message is generated by the business system after receiving the user request message and sent back to the user terminal;

[0031] The first retrieval unit is configured to respond to a verification request message at a preset frequency, retrieve the message data information from a preset interface topic, and parse the message data information to obtain primary key information; wherein, the preset interface topic is located in a first message middleware; the first message middleware is used to store the message data information.

[0032] The second retrieval unit is used to retrieve business data information associated with the primary key information from the business database and to retrieve message data information from the message database based on the primary key information; wherein, the business data information is obtained by the business system parsing the user request message after sending the feedback message, obtaining the original message data information carried in the user request message, and storing the original message data information.

[0033] The determining unit is used to determine the processing result based on the relationship between the service data information and the message data information, and to process the message data information based on the processing result.

[0034] In one example, the identified unit includes:

[0035] The first determining module is configured to determine that the processing result is passed if the business data information exists in the business database and the business data information is consistent with the message data information.

[0036] The second determining module is used to determine that the processing result is unsuccessful if the business data information exists in the business database and the business data information is inconsistent with the message data information.

[0037] The third determining module is used to determine the processing result based on the message data information if the business data information does not exist in the business database but the message data information exists in the message database.

[0038] The fourth determining module is used to determine that the processing result is unsuccessful if the business data information does not exist in the business database and the message data information does not exist in the message database.

[0039] In one example, the third determining module includes:

[0040] The acquisition submodule is used to acquire the data operation type in the message data information;

[0041] The first determining submodule is used to determine that the processing result is passed if the data operation type is a preset type;

[0042] The second determining submodule is used to determine that the processing result is not passed if the data operation type is not a preset type.

[0043] In one example, the identified unit includes:

[0044] The processing module is used to process the next message data information if the processing result is successful.

[0045] The sending module is used to send an alarm message to the user if the processing result is unsuccessful.

[0046] In one example, the receiving unit includes:

[0047] The receiving module is used to receive the message data information and store the message data information in the interface interaction message topic in the second message middleware;

[0048] The sending module is used to send the message data information to the message database through the second message middleware.

[0049] In one example, the device further includes:

[0050] The storage unit is used to store the message data information in the second message middleware into a preset interface topic in the first message middleware according to the data operation type.

[0051] In one example, the data operation type includes at least one of the following: add, delete, modify, and query.

[0052] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0053] The memory stores computer-executed instructions;

[0054] The processor executes computer execution instructions stored in the memory to implement the method as described in the first aspect.

[0055] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in the first aspect.

[0056] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0057] This application provides a message data information processing method, apparatus, device, and storage medium. The method involves receiving message data information and storing it in a message database; responding to verification request messages at a preset frequency, retrieving the message data information from a preset interface topic and parsing it to obtain primary key information; retrieving business data information associated with the primary key information from a business database, and retrieving the message data information from the message database based on the primary key information; determining the processing result based on the relationship between the business data information and the message data information, and processing the message data information based on the processing result. This technical solution enables an accurate data verification mechanism without increasing additional business workload. Attached Figure Description

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

[0059] Figure 1a This is a flowchart illustrating a message data information processing method according to Embodiment 1 of this application;

[0060] Figure 1b This is a schematic diagram of an interaction architecture for message data information provided in Embodiment 1 of this application;

[0061] Figure 2a This is a flowchart illustrating a message data information processing method according to Embodiment 2 of this application;

[0062] Figure 2b This is a schematic diagram of an interaction process provided according to Embodiment 2 of this application;

[0063] Figure 2c This is a schematic diagram illustrating the relationship between business data information and message data information according to Embodiment 2 of this application;

[0064] Figure 3 This is a schematic diagram of a message data information processing device according to Embodiment 3 of this application;

[0065] Figure 4 This is a schematic diagram of the structure of a message data information processing device according to Embodiment 4 of this application;

[0066] Figure 5 This is a block diagram illustrating an electronic device according to an exemplary embodiment.

[0067] The accompanying drawings illustrate specific embodiments of this application, 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 concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0068] 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 numbers 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 application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0069] This application provides a message data information processing method, apparatus, device, and storage medium, which aims to solve the above-mentioned technical problems in the prior art.

[0070] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0071] Figure 1a This is a flowchart illustrating a message data information processing method according to Embodiment 1 of this application. Embodiment 1 includes the following steps:

[0072] S101. Receive message data information and store the message data information in the message database; wherein, the message data information is generated by the business system according to the user request message and sent to the verification system after generation; the user request message is sent from the user terminal to the business system; the feedback message corresponding to the user request message is generated by the business system after receiving the user request message and fed back to the user terminal.

[0073] In this embodiment, the message data information includes the data operation type, request path, operation data information, start time of the data information, and end time of the data information. Specifically, the message data information may include the following:

[0074]

[0075]

[0076] In this embodiment, the message database is used to store message data information exchanged through the interface. If the user request message is an insert request, it can be: proposal / insertProposal. The original message data information in the user request message can be:

[0077]

[0078] The original message data information is a request to the business system to insert an insurance application, with the application number (proposalno) being T001, the start date (startdate) being 2023-01-01, and the end date (enddate) being 2023-12-31.

[0079] In this embodiment, the feedback message can be:

[0080]

[0081] The feedback message above indicates that the business system processed the application successfully (status is 0), and the policy number (proposalno) is T001. However, this does not signify true success, meaning the message data has been successfully inserted into the business database. Successful insertion is only necessary for a specific business scenario, hence the interface response is provided first, followed by asynchronous data processing. Asynchronous data processing means that after the call is issued, the caller can continue performing subsequent operations before receiving the result. Once the call is complete, the caller is typically notified via status, notification, or callback. Asynchronous processing is generally used in transaction scenarios with strict response time requirements.

[0082] In one example, see Figure 1b This diagram illustrates an interactive architecture for message data information. Figure 1b As can be seen, different systems interact through interfaces, and each system possesses its own related database. In this embodiment, the user client sends a user request message to the business system, which then prioritizes responding to the user request message, generating a feedback message, and sending the feedback message back to the user client. The business system then sends the message data to the verification system. This step takes almost negligible time, typically within 10ms, and does not affect the real-time response of the business system's requests.

[0083] S102. In response to a verification request message at a preset frequency, retrieve message data information from a preset interface topic and parse the message data information to obtain primary key information; wherein, the preset interface topic is located in the first message middleware; the first message middleware is used to store message data information.

[0084] In one example, the preset frequency can be one day or T+1, where T is the verification cycle. In this embodiment, the verification request message is initiated by the verification module in the verification system, and the message data information is obtained from the preset interface topic in the first message middleware. The message data information is then parsed to determine the primary key information. In this embodiment, the primary key information can be the insurance policy number T001. Specifically, the message data information obtained from the preset interface topic in the first message middleware is as follows:

[0085]

[0086] S103. Based on the primary key information, retrieve business data information associated with the primary key information from the business database and message data information from the message database; wherein, the business data information is obtained by parsing the user request message after the business system sends the feedback message, obtaining the original message data information carried in the user request message, and storing the original message data information.

[0087] In one example, after determining the primary key information, data information is retrieved from both the business database and the message database based on the primary key information. Specifically, business data associated with the primary key information is retrieved from the business database, and message data stored in S101 is retrieved from the message database. In this embodiment, the message data information is passed to the message database via an interface, and the business data information is obtained by the business system parsing user request messages. Furthermore, the storage of the business data information occurs after the business system sends a feedback message.

[0088] S104. Determine the processing result based on the relationship between business data information and message data information, and process the message data information according to the processing result.

[0089] In this embodiment, business data information represents the data information actually stored in the business database, and message data information represents the data information with feedback messages. Based on the relationship between the two, the processing result can be determined, and the message data information can be further processed based on the processing result.

[0090] This application provides a message data processing method that involves receiving message data and storing it in a message database; responding to verification request messages at a preset frequency, retrieving the message data from a preset interface topic and parsing it to obtain primary key information; retrieving business data associated with the primary key from a business database and retrieving the message data from the message database based on the primary key information; determining the processing result based on the relationship between the business data and the message data, and processing the message data based on the processing result. This technical solution enables an accurate data verification mechanism without increasing additional business workload.

[0091] Figure 2a This is a flowchart illustrating a message data information processing method according to Embodiment 2 of this application. Embodiment 2 includes the following steps:

[0092] S201. Receive message data information and store the message data information in the interface interaction message subject in the second message middleware; wherein, the message data information is generated by the business system according to the user request message and sent to the verification system after generation; the user request message is sent from the user terminal to the business system; the feedback message corresponding to the user request message is generated by the business system after receiving the user request message and fed back to the user terminal.

[0093] In this embodiment, after receiving the message data information sent by the business system, the verification system first stores the message data information in the second message middleware of the verification system. Further, it stores it under the interface interaction message subject in the second message middleware. Specifically, the second message middleware is a supporting software system based on queue and message passing technology, providing synchronous or asynchronous, reliable message transmission for application systems in a network environment. It has multiple advantages such as improved performance through asynchronous processing, reduced coupling, and traffic smoothing, and is widely used in information systems. The benefit of this setup is that in specific scenarios (such as sending SMS verification codes, issuing coupons or vouchers, etc.), the synchronous response and asynchronous processing mode can be used to improve the response time of the system in providing services to the outside world, improve the user experience of the calling party, and shorten the response time by not waiting for all business actions to complete before giving the final feedback.

[0094] S202. Send the message data information to the message database through the second message middleware.

[0095] In this embodiment, the second message middleware in the verification system sends the message data information under the interface interaction message topic to the message database. Specifically, the message data information stored in the message database can be found in Table 1.

[0096] Table 1. Message data information stored in the message database

[0097]

[0098] S203. Store the message data information in the second message middleware into the preset interface topic in the first message middleware according to the data operation type.

[0099] In one example, the data operation types include at least one of the following: add, delete, modify, and query. In this embodiment, the first message middleware is divided into query interface topics, delete interface topics, insert interface topics, and update interface topics according to the data operation type. The message data information in the second message middleware is stored under the above-mentioned interface topics according to the data operation type. For example, if the data operation type of the message data information is insert, then the message data information in the second message middleware is stored under the insert interface topic in the first message middleware. At this time, the preset interface topic is the insert interface topic. The advantage of this setting is that it can check for single or multiple types in different system interaction scenarios (query, insert, delete, modify), flexibly adapting to various situations.

[0100] S204. In response to a verification request message at a preset frequency, retrieve message data information from a preset interface topic, and parse the message data information to obtain primary key information; wherein, the preset interface topic is located in the first message middleware; the first message middleware is used to store message data information.

[0101] For example, this step can refer to step S102 above, and will not be repeated here.

[0102] S205. Based on the primary key information, retrieve business data information associated with the primary key information from the business database and message data information from the message database; wherein, the business data information is obtained by parsing the user request message after the business system sends the feedback message, obtaining the original message data information carried in the user request message, and storing the original message data information.

[0103] To better illustrate the interaction process between the user terminal, business systems, and verification systems, please refer to [link / reference]. Figure 2b The diagram illustrates an interactive process. The advantage of this system setup is that it only adds a single verification trigger action (which can be completed within 10ms) to the existing system's synchronization logic, allowing the entire verification process to be completed with almost no impact on the original system. Furthermore, the subsequent verification process is decoupled from the existing system through a message middleware, improving maintainability, reusability, and scalability. The entire verification system can support multiple systems requiring verification functionality, expanding the application scenarios for the verification system.

[0104] S206. If business data information exists in the business database and the business data information is consistent with the message data information, then the processing result is determined to be successful.

[0105] In this embodiment, if business data information exists in the business database and the business data information is consistent with the message data information, it means that the feedback message responded by the business system will also store the business data information in the business database during the subsequent actual processing. Therefore, the processing result is determined to be successful.

[0106] S207. If business data information exists in the business database, and the business data information and message data information are inconsistent, then the processing result is determined to be unsuccessful.

[0107] In this embodiment, if business data information exists in the business database, but the business data information and message data information are inconsistent, it means that the feedback message responded by the business system did not store the business data information in the business database during the subsequent actual processing. Therefore, the processing result is determined to be unsuccessful.

[0108] S208. If there is no business data information in the business database, but there is message data information in the message database, then the processing result shall be determined based on the message data information.

[0109] In this embodiment, if the business database does not contain business data information, but the message database contains message data information, the processing result needs to be determined based on the data information in the message database. The advantage of this setting is that it considers a normal deletion of business data after the insertion operation but before the verification operation. If this situation is not considered, it would lead to a false alarm because the corresponding primary key information cannot be found in the business database during the insertion operation verification, since the data for that business primary key was deleted before verification, so it is normal that it cannot be found in the business database. Analyzing the message data information existing in the message database can avoid false alarms in this situation.

[0110] In one example, the processing result is determined based on the message data information, including:

[0111] Retrieve the data operation type from the message data information;

[0112] If the data operation type is a preset type, the processing result is determined to be successful;

[0113] If the data operation type is not the preset type, the processing result will be determined as failure.

[0114] In this embodiment, the preset type can be ID, meaning insertion followed by deletion. If the data operation type in the message data information is ID, it indicates that the message data information was inserted and then deleted within the verification period. In this case, it is normal that the data cannot be queried in the business database, and the processing result is determined to be passed. Otherwise, the processing result is determined to be failed.

[0115] S209. If there is no business data information in the business database and no message data information in the message database, the processing result is determined to be unsuccessful.

[0116] In this embodiment, neither the business database nor the message database found the record corresponding to the primary key information, indicating that a problem occurred in the asynchronous storage of business data and no deletion request occurred during the verification period.

[0117] S210. If the processing result is successful, then process the next message data information.

[0118] In this embodiment, if the processing result is successful, the next message data information will be processed.

[0119] S211. If the processing result is unsuccessful, an alarm message will be sent to the user.

[0120] In this embodiment, if the processing result is unsuccessful, an alarm message is sent to the user to remind them to check. For a better explanation, please refer to [link to relevant documentation]. Figure 2c This diagram illustrates the relationship between business data information and message data information.

[0121] This application provides a message data information processing method. If business data information does not exist in the business database, but message data information exists in the message database, the method retrieves the data operation type from the message data information. If the data operation type is a preset type, the processing result is determined to be successful; otherwise, the processing result is determined to be unsuccessful. This technical solution is compatible with different operations on the same business primary key information within a single verification cycle, such as scenarios where insertion is followed by deletion, without causing false alarms.

[0122] Figure 3 This is a schematic diagram of a message data information processing device according to Embodiment 3 of this application. Specifically, the device 30 in Embodiment 3 includes:

[0123] The receiving unit 301 is used to receive message data information and store the message data information in the message database. The message data information is generated by the business system based on the user request message and sent to the verification system after generation. The user request message is sent from the user terminal to the business system. The feedback message corresponding to the user request message is generated by the business system after receiving the user request message and sent back to the user terminal.

[0124] The first retrieval unit 302 is used to respond to a verification request message at a preset frequency, retrieve message data information from a preset interface topic, and parse the message data information to obtain primary key information; wherein, the preset interface topic is located in the first message middleware; the first message middleware is used to store message data information.

[0125] The second retrieval unit 303 is used to retrieve business data information associated with the primary key information from the business database and message data information from the message database based on the primary key information. The business data information is obtained by parsing the user request message after the business system sends the feedback message, obtaining the original message data information carried in the user request message, and storing the original message data information.

[0126] The determining unit 304 is used to determine the processing result based on the relationship between the business data information and the message data information, and to process the message data information based on the processing result.

[0127] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described device can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0128] Figure 4 This is a schematic diagram of a message data information processing device according to Embodiment 4 of this application. Specifically, the device 40 in Embodiment 4 includes:

[0129] The receiving unit 401 is used to receive message data information and store the message data information in the message database; wherein, the message data information is generated by the business system according to the user request message and sent to the verification system after generation; the user request message is sent from the user terminal to the business system; the feedback message corresponding to the user request message is generated by the business system after receiving the user request message and fed back to the user terminal;

[0130] The first retrieval unit 402 is used to respond to a verification request message at a preset frequency, retrieve message data information from a preset interface topic, and parse the message data information to obtain primary key information; wherein, the preset interface topic is located in the first message middleware; the first message middleware is used to store message data information;

[0131] The second retrieval unit 403 is used to retrieve business data information associated with the primary key information from the business database and message data information from the message database based on the primary key information; wherein, the business data information is obtained by parsing the user request message after the business system sends the feedback message, obtaining the original message data information carried in the user request message, and storing the original message data information.

[0132] The determining unit 404 is used to determine the processing result based on the relationship between the business data information and the message data information, and to process the message data information based on the processing result.

[0133] In one example, unit 404 is defined as including:

[0134] The first determining module 4041 is used to determine the processing result as passed if business data information exists in the business database and the business data information is consistent with the message data information.

[0135] The second determining module 4042 is used to determine the processing result as failure if business data information exists in the business database and the business data information and message data information are inconsistent.

[0136] The third determining module 4043 is used to determine the processing result based on the message data if there is no business data information in the business database but there is message data information in the message database.

[0137] The fourth determination module 4044 is used to determine the processing result as failure if there is no business data information in the business database and no message data information in the message database.

[0138] In one example, the third determining module 4043 includes:

[0139] The acquisition submodule 40431 is used to acquire the data operation type in the message data information;

[0140] The first determining submodule 40432 is used to determine the processing result as passed if the data operation type is a preset type;

[0141] The second determining submodule 40433 is used to determine the processing result as failing if the data operation type is not a preset type.

[0142] In one example, unit 404 is defined as including:

[0143] The processing module 4045 is used to process the next message data information if the processing result is successful.

[0144] The sending module 4046 is used to send an alarm message to the user if the processing result is unsuccessful.

[0145] In one example, receiving unit 401 includes:

[0146] The receiving module 4011 is used to receive message data information and store the message data information in the interface interaction message topic in the second message middleware.

[0147] The sending module 4012 is used to send message data information to the message database through the second message middleware.

[0148] In one example, device 40 further includes:

[0149] Storage unit 405 is used to store message data information in the second message middleware into a preset interface topic in the first message middleware according to the data operation type.

[0150] In one example, the data operation type includes at least one of the following: add, delete, modify, query.

[0151] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described device can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0152] Figure 5 This is a block diagram illustrating an electronic device according to an exemplary embodiment. The device may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.

[0153] The device 500 may include one or more of the following components: a processing component 502, a memory 504, a power supply component 506, a multimedia component 508, an audio component 510, an input / output (I / O) interface 512, a sensor component 514, and a communication component 516.

[0154] Processing component 502 typically controls the overall operation of device 500, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 502 may include one or more modules to facilitate interaction between processing component 502 and other components. For example, processing component 502 may include a multimedia module to facilitate interaction between multimedia component 508 and processing component 502.

[0155] Memory 504 is configured to store various types of data to support the operation of device 500. Examples of such data include instructions for any application or method operating on device 500, contact data, phonebook data, messages, pictures, videos, etc. Memory 504 can 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.

[0156] Power supply component 506 provides power to various components of device 500. Power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 500.

[0157] Multimedia component 508 includes a screen that provides an output interface between device 500 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 508 includes a front-facing camera and / or a rear-facing camera. When device 500 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0158] Audio component 510 is configured to output and / or input audio signals. For example, audio component 510 includes a microphone (MIC) configured to receive external audio signals when device 500 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 504 or transmitted via communication component 516. In some embodiments, audio component 510 also includes a speaker for outputting audio signals.

[0159] I / O interface 512 provides an interface between processing component 502 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0160] Sensor assembly 514 includes one or more sensors for providing status assessments of various aspects of device 500. For example, sensor assembly 514 may detect the on / off state of device 500, the relative positioning of components such as the display and keypad of device 500, changes in the position of device 500 or a component of device 500, the presence or absence of user contact with device 500, the orientation or acceleration / deceleration of device 500, and temperature changes of device 500. Sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 514 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0161] Communication component 516 is configured to facilitate wired or wireless communication between device 500 and other devices. Device 500 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 516 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 516 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0162] In an exemplary embodiment, the apparatus 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0163] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 504 including instructions, which can be executed by a processor 520 of the device 500 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0164] A non-transitory computer-readable storage medium, wherein when the instructions in the storage medium are executed by the processor of an electronic device, the electronic device is able to perform the aforementioned message data information processing method of the electronic device.

[0165] This application also discloses a computer program product, including a computer program that, when executed by a processor, implements the method described in this embodiment.

[0166] Various embodiments of the systems and technologies described above in this application can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0167] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or electronic device.

[0168] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0169] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0170] The systems and technologies described herein can be implemented in computing systems that include back-end components (e.g., as data electronic devices), or computing systems that include middleware components (e.g., application electronic devices), or computing systems that include front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0171] Computer systems can include client and electronic devices. Clients and electronic devices are generally geographically separated and typically interact via communication networks. The client-electronic device relationship is created by computer programs running on the respective computers and having a client-electronic device relationship with each other. The electronic device can be a cloud electronic device, also known as a cloud computing electronic device or cloud host, a host product within the cloud computing service system, addressing the shortcomings of traditional physical hosts and VPS services ("Virtual Private Server," or simply "VPS") in terms of management difficulty and weak business scalability. The electronic device can also be an electronic device in a distributed system or an electronic device incorporating blockchain technology. It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this application is achieved, and this is not limited herein.

[0172] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application 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 application are indicated by the following claims.

[0173] It should be understood that this application is not limited to the precise structure 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 application is limited only by the appended claims.

Claims

1. A method for processing message data information, characterized in that, The method includes: The system receives message data and stores it in a message database. The message data is generated by the business system based on a user request message and sent to the verification system after generation. The user request message is sent from the user terminal to the business system. The feedback message corresponding to the user request message is generated by the business system after receiving the user request message and sent back to the user terminal. In response to a verification request message at a preset frequency, the message data information is retrieved from a preset interface topic and parsed to obtain primary key information; wherein, the preset interface topic is located in a first message middleware; the first message middleware is used to store the message data information; Based on the primary key information, business data information associated with the primary key information is retrieved from the business database, and message data information is retrieved from the message database; wherein, the business data information is obtained by the business system parsing the user request message after sending the feedback message, obtaining the original message data information carried in the user request message, and storing the original message data information; Based on the relationship between the business data information and the message data information, the processing result is determined, and the message data information is processed according to the processing result.

2. The method according to claim 1, characterized in that, The step of determining the processing result based on the relationship between the business data information and the message data information includes: If the business data information exists in the business database and the business data information is consistent with the message data information, then the processing result is determined to be successful. If the business data information exists in the business database, and the business data information and the message data information are inconsistent, then the processing result is determined to be unsuccessful. If the business data information does not exist in the business database, but the message data information exists in the message database, then the processing result is determined based on the message data information. If the business data information does not exist in the business database and the message data information does not exist in the message database, then the processing result is determined to be unsuccessful.

3. The method according to claim 2, characterized in that, The step of determining the processing result based on the message data information includes: Obtain the data operation type from the message data information; If the data operation type is a preset type, then the processing result is determined to be passed; If the data operation type is not a preset type, the processing result is determined to be unsuccessful.

4. The method according to claim 2 or 3, characterized in that, The step of processing the message data information based on the processing result includes: If the processing result is successful, then process the next message data information; If the processing result is unsuccessful, an alarm message will be sent to the user.

5. The method according to claim 1, characterized in that, The receiving of message data information and the storage of the message data information in the message database include: Receive the message data information and store the message data information under the interface interaction message topic in the second message middleware; The message data information is sent to the message database through the second message middleware.

6. The method according to claim 5, characterized in that, Before retrieving the message data information from the preset interface topic in response to the verification request message at a preset frequency, the method further includes: The message data information in the second message middleware is stored under a preset interface topic in the first message middleware according to the data operation type.

7. The method according to claim 3 or 6, characterized in that, The data operation types include at least one of the following: add, delete, modify, and query.

8. A message data information processing device, characterized in that, The device includes: A receiving unit is configured to receive message data information and store the message data information in a message database; wherein the message data information is generated by the business system based on a user request message and sent to the verification system after generation; the user request message is sent from the user terminal to the business system; the feedback message corresponding to the user request message is generated by the business system after receiving the user request message and sent back to the user terminal; The first retrieval unit is configured to respond to a verification request message at a preset frequency, retrieve the message data information from a preset interface topic, and parse the message data information to obtain primary key information; wherein, the preset interface topic is located in a first message middleware; the first message middleware is used to store the message data information. The second retrieval unit is used to retrieve business data information associated with the primary key information from the business database and to retrieve message data information from the message database based on the primary key information; wherein, the business data information is obtained by the business system parsing the user request message after sending the feedback message, obtaining the original message data information carried in the user request message, and storing the original message data information. The determining unit is used to determine the processing result based on the relationship between the service data information and the message data information, and to process the message data information based on the processing result.

9. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-7.

10. 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 method as described in any one of claims 1-7.

11. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method as described in any one of claims 1-7.

Images