Message processing method and device, equipment and readable medium
By parsing and updating message processing in the information database, using asynchronous message storage system and message queues, the performance degradation and data consistency problems of traditional message processing methods in high concurrent systems are solved, and system availability and user experience are improved.
Patent Information
- Application Number
- CN202411255618.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-06
- Publication Date
- 2024-12-06
AI Technical Summary
Traditional message processing methods have degraded performance in high-concurrency and low-latency systems, which may lead to data consistency problems, and the processing of unstructured or semi-structured messages is complex, increasing the difficulty of analysis.
Provide a message processing method, by parsing received messages and storing them in the information database, including updates to push requests and receipt status, using asynchronous message storage system and message queues for processing, alleviating database write pressure and improving read performance .
Implement decoupling and flexible flow control, utilize the peak-cutting and valley-filling capabilities of message queues, improve system availability and user experience, and reduce data consistency problems and analysis complexity.
Smart Images

Figure CN119094489A_ABST
Abstract
Description
Technical Field
[0001] Example embodiments of the present disclosure generally relate to the field of computer technology, and more particularly, to methods, apparatuses, devices, and computer-readable storage media for message processing. Background Art
[0002] With the development of information technology, message processing technology plays an important role in operators' short message processing, users' short message processing and other intermediate messages. Traditional message technology can process messages, but it also has many problems. Summary of the invention
[0003] In a first aspect of the present disclosure, a method for message processing is provided. The method includes: in response to receiving a first message, parsing the first message and storing the parsed first message in an information library, the first message including information of at least one account corresponding to the push request message; in response to receiving a second message, parsing the second message and updating the push request status in the information library based on the parsed second message, the second message including the push request status corresponding to at least one account that sent the push request message; and in response to receiving a third message, parsing the third message and updating the push receipt status in the information library based on the parsed third message, the third message including the push receipt status corresponding to at least one account that sent the push request message.
[0004] In the second aspect of the present disclosure, a device for message processing is provided. The device includes: an information storage module, configured to parse the first message in response to receiving a first message and store the parsed first message in an information base, the first message including information of at least one account corresponding to the push request message; a request status update module, configured to parse the second message in response to receiving a second message and update the push request status in the information base based on the parsed second message, the second message including the push request status corresponding to at least one account sending the push request message; and a receipt status update module, configured to parse the third message in response to receiving a third message and update the push receipt status in the information base based on the parsed third message, the third message including the push receipt status corresponding to at least one account sending the push request message.
[0005] In a third aspect of the present disclosure, an electronic device is provided. The electronic device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit, and when the instructions are executed by the at least one processing unit, the electronic device executes the method of the first aspect of the present disclosure.
[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to perform the method according to the first aspect of the present disclosure.
[0007] It should be understood that the contents described in the summary of the invention are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] In the following, in conjunction with the accompanying drawings and with reference to the following detailed description, the above and other features, advantages and aspects of various implementations of the present disclosure will become more apparent. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:
[0009] Figure 1 A schematic diagram showing an example environment in which embodiments of the present disclosure can be implemented;
[0010] Figure 2 A flowchart showing a process for message processing according to some embodiments of the present disclosure is shown;
[0011] Figure 3 A schematic diagram showing a process for message processing according to some embodiments of the present disclosure is shown;
[0012] Figure 4 A schematic structural block diagram of an apparatus for message processing according to some embodiments of the present disclosure is shown; and
[0013] Figure 5 A block diagram of an electronic device is shown in which one or more embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION
[0014] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0015] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.
[0016] It should be noted that the acquisition, storage and application of user personal information involved in the technical solution of the present disclosure are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0017] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.
[0018] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information, so that the user can independently choose whether to provide personal information to software or hardware such as electronic devices, applications, servers or storage media that execute operations of the technical solution of the present disclosure based on the prompt message.
[0019] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information is sent to the user in a manner such as a pop-up window, in which the prompt information can be presented in text form. In addition, the pop-up window can also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.
[0020] Traditionally, message processing methods mainly include synchronous message storage methods. Although synchronous message storage methods can also store received messages, they have many problems. On the one hand, in terms of performance, collecting, recording and storing synchronous messages at runtime may affect the performance of the program because additional resources are required to perform these operations. For example, in a system with high concurrency and low latency requirements, recording synchronous messages may cause system performance to degrade. On the other hand, recording synchronous messages may introduce data consistency issues. If there is a delay between the recording of synchronous messages and the actual operation or an error occurs during the recording process, the recorded message may be inconsistent with the information in the actual message, affecting subsequent analysis and troubleshooting. On the other hand, the synchronous messages stored in the library may be unstructured or semi-structured. Unstructured or semi-structured messages require appropriate data analysis and mining to obtain the information therein. Professional data analysts or tools are required for professional processing, which increases the complexity of the analysis.
[0021] In view of this, an embodiment of the present disclosure provides a scheme for message processing. The scheme includes: in response to receiving a first message, parsing the first message and storing the parsed first message in an information library, the first message includes information of at least one account corresponding to the push request message; in response to receiving a second message, parsing the second message and updating the push request status in the information library based on the parsed second message, the second message includes the push request status corresponding to at least one account that sends the push request message; and in response to receiving a third message, parsing the third message and updating the push receipt status in the information library based on the parsed third message, the third message includes the push receipt status corresponding to at least one account that sends the push request message. In this way, the message storage can be processed through the corresponding module, with the advantages of decoupling and flexible flow control, and at the same time, the peak-shaving and valley-filling capabilities of the message queue can be utilized to reduce the write pressure of the database, improve the read performance changes of the database, and improve the availability and user experience of the system.
[0022] Figure 1 1 is a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. Figure 1 As shown, the environment 100 may include an electronic device 110 , which may include an asynchronous message storage system 120 , which may include a traffic entry module 125 , a scheduling service module 130 , a message queue module 135 , and an asynchronous information storage module 140 .
[0023] The electronic device 110 is at least configured to store the received message.
[0024] In an embodiment of the present disclosure, in order to store received messages, before the messages are stored, the user can perform a series of configurations on the asynchronous message storage system 120 through the electronic device 110 to initialize the resources included in the traffic entry module 125, the scheduling service module 130, the message queue module 135 and the asynchronous information storage module 140.
[0025] In some embodiments, the asynchronous message storage system 120 may be deployed in the electronic device 110. The asynchronous message storage system 120 may communicate with the electronic device 110 to obtain data and / or files required to initialize the received message from the electronic device 110. The asynchronous message storage system 120 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks, and big data and artificial intelligence platforms. The asynchronous message storage system 120 may include, for example, a computing system / server, such as a mainframe, an edge computing node, a computing device in a cloud environment, and the like.
[0026] A communication connection may be established between the asynchronous message storage system 120 and the electronic device 110. The communication connection may be established in a wired manner or a wireless manner. The communication connection may include, but is not limited to, a Bluetooth connection, a mobile network connection, a Universal Serial Bus (USB) connection, a Wireless Fidelity (WiFi) connection, etc., and the embodiments of the present disclosure are not limited in this respect. In the embodiments of the present disclosure, the asynchronous message storage system 120 and the electronic device 110 may implement signaling interaction through the communication connection between the two.
[0027] The electronic device 110 may include any computing system with computing capabilities, such as various computing devices / systems, terminal devices, server devices, etc. The terminal device may be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a handheld computer, a portable game terminal, a VR / AR device, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an e-book device, a game device, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof.
[0028] It should be understood that the structure and function of the various elements in the environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.
[0029] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.
[0030] Figure 2 1 shows a flowchart of a process 200 for message processing according to some embodiments of the present disclosure. The process 200 may be implemented at the electronic device 110. For ease of discussion, reference will be made to Figure 1 The process 200 is described with reference to the environment 100 of FIG.
[0031] The traffic entry module 125 receives a push request from at least one account, and pushes the first message queue to the message queue module 135. The message queue module 135 receives the first message queue (Message Queue, MQ), parses the first message queue to obtain a first message, and sends the corresponding first message to the asynchronous information storage module 140 through the first message carrier. The asynchronous information storage module 140 receives and parses the first message, and stores the parsed first message in the information library.
[0032] In some embodiments, each first message in the first message queue includes account information of at least one account that sends a push request message. The account that sends the push request message, and the corresponding account information may include basic information, push request status, and push receipt status.
[0033] When the traffic entry module 125 completes pushing the first message queue to the message queue module 135, the traffic entry module 125 pushes the second message queue to the message queue module 135. The message queue module 135 receives the second message and sends the corresponding second message to the asynchronous information storage module 140 through the second message carrier. The asynchronous information storage module 140 receives and parses the second message, and updates the push request status in the information library based on the parsed second message.
[0034] In some embodiments, each second message in the second message queue includes a push request status corresponding to at least one account that sends the push request message.
[0035] In some embodiments, the push request status may include a push request success or a push request failure, where each status has a corresponding status bit, and the status bit is used to represent the current status information. For example, the status position 1 may correspond to a push request success, and the status position 0 may correspond to a push request failure.
[0036] The scheduling service module 130 pulls at least one receipt information from the information library. The scheduling service module 130 pushes the third message queue to the message queue module 135 based on the at least one receipt information pulled. In some embodiments, each third message in the third message queue includes a push receipt status corresponding to at least one account that sends the push request message. The message queue module 135 receives the third message and sends the corresponding third message to the asynchronous information storage module 140 through the third message carrier. The asynchronous information storage module 140 receives and parses the third message, and updates the push receipt status in the information library based on the parsed third message.
[0037] In some embodiments, the push receipt status may include push receipt success and push receipt failure, where each status has a corresponding status bit, for example, the status position 1 corresponding to the push receipt success and the status position 0 corresponding to the push receipt failure.
[0038] In some embodiments, if the asynchronous information storage module 140 has not completed storing the basic information in the account information, the asynchronous information storage module 140 cannot successfully update the push receipt status in the current account information; if the asynchronous information storage module 140 completes the basic information, the asynchronous information storage module 140 can successfully update the push receipt status in the current account information.
[0039] In some embodiments, if the current third message cannot update the push receipt status, the current third message is determined as invalid receipt information, and at least one invalid receipt information is stored in an invalid receipt information library of the information library.
[0040] In some embodiments, the scheduling service module 130 executes to pull at least one receipt information from the information library, and completes the push receipt status update corresponding to the account that sends the push request message in the information library by communicating with the message queue module 135 and the asynchronous information storage module 140. There may be a part of the account information in which the basic information has not been stored. At this time, the receipt status in the account information of this part of the account cannot be updated successfully. It is necessary to pull the invalid receipt information that could not be successfully updated last time at the preset time, and update the receipt status of this part of the account again.
[0041] The scheduling service module 130 pulls at least one invalid receipt information stored in the invalid receipt information library. The scheduling service module 130 pushes the fourth message queue to the message queue module 135 based on the at least one invalid receipt information pulled. Each fourth message in the fourth message queue includes at least one invalid receipt information. The message queue module 135 receives the fourth message queue and sends the corresponding fourth message in the fourth message queue to the asynchronous information storage module 140 through the fourth message carrier. The asynchronous information storage module 140 parses the fourth message and updates the information library based on the parsed fourth message to store the receipt status of at least one account without a receipt status, so as to store the complete account information corresponding to the account that sends the push request message in the information library.
[0042] In some embodiments, in the above process 200, any two modules of the traffic entry module 125, the message queue module 135, the scheduling service module 130 and the asynchronous information storage module 140 can be operated asynchronously, and each module will process the information received and send it to the corresponding other modules.
[0043] In some embodiments, the information stored in the asynchronous information storage module 140 may be a text message or some intermediate information data; the message carrier may be represented as Consume TopicC Message, and the push queue message may be represented as Push TopicA Message, Push TopicB Message, etc.
[0044] In some embodiments, different message carriers may be used to process information from different sources, thereby releasing the coupling relationship between programs and reducing the situation where program flow abnormal terminations are caused by persistent data.
[0045] Figure 3 FIG. 3 is a flowchart of a process 300 for message processing according to some embodiments of the present disclosure. The process 300 may be implemented at the electronic device 110. For ease of discussion, reference will be made to FIG. Figure 1 The process 300 is described with reference to the environment 100 of FIG.
[0046] In some embodiments, the electronic device 110 may include a traffic entry module 125 , a scheduling service module 130 , a message queue module 135 , and an asynchronous information storage module 140 .
[0047] In block 310 , in response to receiving the first message, the message queue module 135 parses the first message and stores the parsed first message in an information repository.
[0048] In some embodiments, the first message may include information of at least one account corresponding to the sending of the push request message.
[0049] In some embodiments, the traffic entry module 125 may receive a push request from at least one account. In other embodiments, in response to the push request, the traffic entry module 125 may push the first message queue. Specifically, each first message in the first message queue includes information of at least one account that sends the push request message. In other embodiments, in response to receiving the first message, the message queue module 135 may send the corresponding first message to the asynchronous information storage module 140 through the first message carrier.
[0050] In block 320 , in response to receiving the second message, the message queue module 135 parses the second message and updates the push request status in the information repository based on the parsed second message.
[0051] In some embodiments, the second message may include a push request status corresponding to at least one account that sent the push request message.
[0052] In some embodiments, the traffic inlet module 125 may push a second message queue. Specifically, each second message in the second message queue may include a push request status corresponding to at least one account that sends a push request message. In other embodiments, in response to receiving the second message, the message queue module 135 may send the corresponding second message to the asynchronous information storage module 140 via the second message carrier.
[0053] In block 330 , in response to receiving the third message, the message queue module 135 parses the third message and updates the push receipt status in the information repository based on the parsed third message.
[0054] In some embodiments, the scheduling service module 130 can pull at least one receipt information from the information library. In other embodiments, the scheduling service module 130 can push a third message queue based on the at least one receipt information pulled. Specifically, each third message in the third message queue may include a push receipt status corresponding to at least one account that sends a push request message. In other embodiments, in response to receiving the third message, the message queue module 135 sends the corresponding third message to the asynchronous information storage module 140 via the third message carrier. In more embodiments, if the current third message cannot update the push receipt status, the current third message is determined to be invalid receipt information. In addition, at least one invalid receipt information can be stored in the information library.
[0055] In some embodiments, the scheduling service module 130 may pull at least one invalid receipt information stored in the information library. In other embodiments, the scheduling service module 130 may push a fourth message queue based on the pulled at least one invalid receipt information. Specifically, each fourth message in the fourth message queue includes at least one invalid receipt information. In other embodiments, in response to receiving the fourth message queue, the message queue module 135 may send the corresponding fourth message in the fourth message queue through the fourth message carrier. In more embodiments, the asynchronous information storage module 140 parses the fourth message and updates the information library to store the receipt status of at least one account without a receipt status based on the parsed fourth message.
[0056] In summary, the embodiments of the present disclosure can process information storage using the asynchronous information storage module 140, which has the advantages of decoupling and flexible flow control. At the same time, the scheduling capability of the message queue can reduce the write pressure of the database, improve the read performance change of the database, improve the system's availability and user experience, and can also parse and process the data generated during the operation of the system and then persist it. During the program running process, there will be no system abnormalities and interruptions due to persistent data, which can improve system stability.
[0057] The embodiments of the present disclosure also provide corresponding devices for implementing the above methods or processes. Figure 4 A schematic structural block diagram of an apparatus 400 for message processing according to some embodiments of the present disclosure is shown. The apparatus 400 may be implemented as or included in the electronic device 110. Each module / component in the apparatus 400 may be implemented by hardware, software, firmware or any combination thereof.
[0058] like Figure 4As shown, the device 400 includes an information storage module 410, which is configured to parse the first message in response to receiving a first message and store the parsed first message in an information library, the first message including information of at least one account corresponding to the push request message. The device 400 also includes a request status update module 420, which is configured to parse the second message in response to receiving a second message and update the push request status in the information library based on the parsed second message, the second message including the push request status corresponding to at least one account that sent the push request message. The device 400 also includes a receipt status update module 430, which is configured to parse the third message in response to receiving a third message and update the push receipt status in the information library based on the parsed third message, the third message including the push receipt status corresponding to at least one account that sent the push request message.
[0059] In some embodiments, the device 400 also includes a first message processing module, which is configured to receive a push request from at least one account; in response to the push request, push the first message queue, each first message in the first message queue includes information of at least one account that sends the push request message; and in response to receiving the first message, send the corresponding first message to the asynchronous information storage module through the first message carrier.
[0060] In some embodiments, the request status update module 420 is also configured as a second message processing module, configured to push a second message queue, each second message in the second message queue includes a push request status corresponding to at least one account that sends a push request message; and in response to receiving the second message, sending the corresponding second message to the asynchronous information storage module through the second message carrier.
[0061] In some embodiments, the device 400 also includes a third information processing module, which is configured to pull at least one receipt information from the information library; push a third message queue based on the at least one receipt information pulled, and each third message in the third message queue includes a push receipt status corresponding to at least one account that sends a push request message; and in response to receiving the third message, send the corresponding third message to the asynchronous information storage module via the third message carrier.
[0062] In some embodiments, the third information processing module is further configured to determine the current third message as invalid receipt information if the current third message cannot update the push receipt status, and at least one invalid receipt information is stored in the information library.
[0063] In some embodiments, where the information repository stores an updateable receipt status of at least one account without a receipt status, the device 400 also includes a fourth message processing module, which is configured to send a corresponding fourth message in the fourth message queue through a fourth message carrier in response to receiving a fourth message queue; and parse the fourth message and update the receipt status of at least one account without a receipt status stored in the information repository based on the parsed fourth message.
[0064] In some embodiments, before sending the corresponding fourth message through the fourth message carrier, the fourth message processing module is also configured to pull at least one invalid receipt information stored in the information library; and based on the pulled at least one invalid receipt information, push the fourth message queue, and each fourth message in the fourth message queue includes at least one invalid receipt information.
[0065] The units and / or modules included in the device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units and / or modules can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the units and / or modules in the device 400 can be implemented at least in part by one or more hardware logic components. As an example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.
[0066] It should be understood that one or more steps in the above method can be performed by a suitable electronic device or a combination of electronic devices. Such an electronic device or a combination of electronic devices may include, for example, Figure 1 The electronic device 110 in.
[0067] Figure 5 1 shows a block diagram of an electronic device 500 in which one or more embodiments of the present disclosure may be implemented. It should be understood that Figure 5 The electronic device 500 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. Figure 5 The electronic device 500 shown can be used to implement Figure 1 An electronic device 110.
[0068] like Figure 5As shown, the electronic device 500 is in the form of a general electronic device. The components of the electronic device 500 may include, but are not limited to, one or more processors or processing units 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 520. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 500.
[0069] The electronic device 500 typically includes a plurality of computer storage media. Such media may be any available media accessible to the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 may be a volatile memory (e.g., registers, caches, random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and / or data and may be accessed within the electronic device 500.
[0070] The electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 5 As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 520 may include a computer program product 525 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.
[0071] The communication unit 540 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 500 can be implemented in a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 500 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.
[0072] The input device 550 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 560 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 500 may also communicate with one or more external devices (not shown) through the communication unit 540 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 500, or communicate with any device that allows the electronic device 500 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).
[0073] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.
[0074] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.
[0075] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0076] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0077] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.
[0078] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.
Claims
1. A message processing method, comprising: In response to receiving a first message, parsing the first message and storing the parsed first message in an information repository, the first message including information of at least one account corresponding to the sending push request message; In response to receiving a second message, parsing the second message and updating the push request status in the information base based on the parsed second message, the second message including the push request status corresponding to the at least one account sending the push request message; as well as In response to receiving a third message, the third message is parsed and the push receipt status in the information library is updated based on the parsed third message, the third message including the push receipt status corresponding to the at least one account that sends the push request message.
2. The method according to claim 1, further comprising: receiving a push request from the at least one account; In response to the push request, push a first message queue, each first message in the first message queue includes information of the at least one account that sends the push request message; as well as In response to receiving the first message, a corresponding first message is sent to the asynchronous information storage module via the first message carrier.
3. The method according to claim 1, further comprising: Pushing a second message queue, each second message in the second message queue includes a push request status corresponding to the at least one account that sends the push request message; as well as In response to receiving the second message, a corresponding second message is sent to the asynchronous information storage module via a second message carrier.
4. The method according to claim 1, further comprising: Pulling at least one receipt information from the information library; Pushing a third message queue based on the at least one receipt information pulled, each third message in the third message queue includes a push receipt status corresponding to the at least one account that sends the push request message; as well as In response to receiving the third message, a corresponding third message is sent to the asynchronous information storage module via a third message carrier.
5. The method according to claim 4, further comprising: If the current third message cannot update the push receipt status, the current third message is determined as invalid receipt information, and at least one of the invalid receipt information is stored in the information library.
6. The method according to claim 1, wherein the information repository stores at least one updateable receipt status of an account without a receipt status, the method further comprising: In response to receiving a fourth message queue, sending a fourth message corresponding to the fourth message queue through a fourth message carrier; as well as The fourth message is parsed and based on the parsed fourth message, the information library is updated to store the receipt status of the at least one account without a receipt status.
7. The method according to claim 6, wherein before sending the corresponding fourth message through the fourth message carrier, the method further comprises: Pulling at least one invalid receipt information stored in the information database; as well as Based on the at least one invalid receipt information pulled, the fourth message queue is pushed, and each fourth message in the fourth message queue includes at least one invalid receipt information.
8. A device for message processing, comprising: An information storage module, configured to parse a first message in response to receiving the first message and store the parsed first message in an information repository, wherein the first message includes information of at least one account corresponding to the sending push request message; a request status updating module, configured to, in response to receiving a second message, parse the second message and update the push request status in the information base based on the parsed second message, wherein the second message includes the push request status corresponding to the at least one account that sends the push request message; as well as The receipt status update module is configured to parse the third message in response to receiving a third message and update the push receipt status in the information library based on the parsed third message, wherein the third message includes the push receipt status corresponding to the at least one account that sends the push request message.
9. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the electronic device to perform the method according to any one of claims 1 to 7.
10. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 7.
