Downlink message flood peak processing method and device, electronic equipment, storage medium and program product
By introducing concurrency control methods such as command boards and message queues, combined with real-time processing and buffering, the processing efficiency problem caused by rate limiting in the electronic commercial bill system was solved, achieving efficient and stable message processing.
Patent Information
- Application Number
- CN202510980761.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-16
- Publication Date
- 2025-11-07
AI Technical Summary
In existing technologies, internal flow control affects message processing efficiency, resulting in insufficient processing capacity of electronic commercial bill systems, which cannot meet the requirements of high efficiency and high stability.
By introducing command tokens and command message queues, and adopting a combination of real-time processing and buffered processing, downlink messages are received and concurrent control is performed. If the token is successfully extracted, it is processed in real time; otherwise, the message is pushed to the message queue for buffered processing.
It improves downlink message processing efficiency, ensures high efficiency and stability in message processing, and avoids the impact of internal system rate limiting.
Smart Images
Figure CN120915731A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of electronic commercial bills, and in particular to a downlink message flood processing method and device, electronic equipment, a storage medium and a program product. BACKGROUND
[0002] Currently, electronic commercial bills are connected to the Shanghai bill exchange through a message middleware, and the processing of downlink messages is an important work, which must ensure the high efficiency and high stability of message processing. If the message processing is slow, the message queue at the bill exchange end is long, indicating that there is a message lag, which produces business risk. Taking the expiration centralized clearing as an example, the centralized issuance of messages triggers the flow limiting of core account transactions, which needs to be able to call the core account transaction smoothly on the basis of efficiently consuming the bill exchange messages, and the actual influence on the host is smooth.
[0003] Due to the sensitivity of the third-party message processing of the People's Bank of China and the bill exchange, the general member end adopts the message listener mode to consume messages from the message queue, and by adjusting the number of threads of the message listener or expanding the number of servers, the message processing throughput can be quickly increased. In the current situation, all message messages need to be processed per second.
[0004] However, the increase of message speed also poses a challenge to the member's internal system, which needs to support corresponding concurrency and improve the processing capacity. However, due to the complexity of the member's internal systems and the corresponding historical characteristics, the processing capacity of some internal systems cannot reach the capacity of the message processing engine, triggering the internal flow limiting of the corresponding system, and further affecting the message processing efficiency. SUMMARY
[0005] The present application provides a downlink message flood processing method, device, electronic equipment, storage medium and program product to solve the problem of affecting message processing efficiency due to internal flow limiting in the prior art.
[0006] According to an aspect of the present application, a downlink message flood processing method is provided, the method comprising:
[0007] receiving a downlink message and extracting a token from an instruction token;
[0008] if the token extraction is successful, calling an associated account system to process the downlink message in real time, and returning the token;
[0009] if the token extraction is not successful, pushing the downlink message to an instruction message queue, and using an asynchronous task to poll the instruction message queue in real time to buffer process the downlink message stored in the instruction message queue.
[0010] According to another aspect of the present application, there is provided a downlink message flood processing device, the device comprising:
[0011] a downlink message receiving module, configured to receive a downlink message and extract a token from the token;
[0012] a downlink message real-time processing module, configured to, if the token extraction is successful, call an associated accounting system to perform real-time processing on the downlink message and return the token;
[0013] a downlink message buffer processing module, configured to, if the token extraction is not successful, push the downlink message to an instruction message queue and use an asynchronous task to poll the instruction message queue in real time to perform buffer processing on the downlink message stored in the instruction message queue.
[0014] According to another aspect of the present application, there is provided an electronic device, the electronic device comprising:
[0015] at least one processor; and
[0016] a memory connected to the at least one processor in communication; wherein,
[0017] the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to perform the downlink message flood processing method according to any one of the embodiments of the present application.
[0018] According to another aspect of the present application, there is provided a computer readable storage medium storing computer instructions for causing a processor to implement the downlink message flood processing method according to any one of the embodiments of the present application when executed by the processor.
[0019] According to another aspect of the present application, there is provided a computer program product comprising a computer program for implementing the downlink message flood processing method according to any one of the embodiments of the present application when executed by a processor.
[0020] The technical scheme of the embodiment of the present application receives a downlink message, extracts a token from the token, if the token extraction is successful, calls an associated account system to perform real-time processing on the downlink message, and returns the token, if the token extraction is not successful, pushes the downlink message to a command message queue, and uses an asynchronous task to perform real-time polling on the command message queue to perform buffer processing on the downlink message stored in the command message queue. The problem of affecting the processing efficiency of the message due to internal flow limiting in the prior art is solved. By introducing the token and the command message queue for concurrent control, the downlink message is processed in a manner of combining real-time processing and buffer processing, and the beneficial effect of improving the processing efficiency of the downlink message is obtained.
[0021] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present application, nor is it used to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS
[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.
[0023] Figure 1 is a flow chart of a downlink message flood processing method according to the first embodiment of the present application;
[0024] Figure 2 is a downlink message schematic diagram in the prior art according to the first embodiment of the present application;
[0025] Figure 3 is a downlink message introduction command message queue schematic diagram according to the first embodiment of the present application;
[0026] Figure 4 is a flow chart of a downlink message flood processing method according to the second embodiment of the present application;
[0027] Figure 5 is a flow chart of a downlink message flood buffer processing method according to the second embodiment of the present application;
[0028] Figure 6 is a structural schematic diagram of a downlink message flood processing device according to the third embodiment of the present application;
[0029] Figure 7 is a structural schematic diagram of an electronic device according to the fourth embodiment of the present application. DETAILED DESCRIPTION
[0030] In order to make the personnel in the technical field better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work should belong to the scope of protection of the present application.
[0031] It should be noted that the terms "first", "second", "target", "original" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include", "equal" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.
[0032] Embodiment one
[0033] Figure 1 A flowchart of a downlink message flood processing method is provided for the first embodiment of the present application. The present embodiment can be applied to the case where the downlink message flood is processed by combining real-time processing and instruction message queue buffer processing. The method can be executed by a downlink message flood processing device, which can be realized in the form of hardware and / or software, and can be configured in any electronic device with network communication function. As shown in the figure, the method comprises the following steps. Figure 1
[0034] S110, receiving a downlink message and extracting a token from a token.
[0035] As shown in the figure, the method comprises the following steps. Figure 2 As shown, the ticket exchange has more message channels to the bill system, and the downlink speed is faster. However, the bill system to the financial system is limited by performance and other factors, and the message processing channel is less, which causes channel mismatch, overall processing performance decline, and further affects the overall stability of the bill business. Therefore, it is necessary to introduce a buffer mechanism between the bill system and the financial system, which can ensure the processing performance of the downlink message of the ticket exchange, and on the other hand, ensure that all messages call the internal system in a gentle way, and ensure the stability and correctness of the business.
[0036] Therefore, the embodiment of the present application constructs a downlink message flood processing method, as shown in the accompanying drawings. Figure 3 As shown, the instruction token and the instruction message queue are introduced into the bill system to buffer the downlink message when the bill system sends the message to the associated financial system.
[0037] The downlink message can be data information or control instructions sent from the center node to the terminal device, and the transmission direction is from the center node to the terminal device, that is, from top to bottom. For example, the ticket exchange sends the message to the bill system, at this time the ticket exchange is the center node, the bill system is the terminal device, and the transmitted message is the downlink message; when the bill system sends the message to the associated financial system, the bill system is the center node and the associated financial system is the terminal device, and the transmitted message is the downlink message.
[0038] The instruction token can be used to control the number of concurrent calls to the associated financial system. When the bill system can normally obtain a token from the instruction token, the associated financial system can be called to send the message.
[0039] S120, if the token extraction is successful, the associated accounting system is called to process the downlink message in real time, and the token is returned.
[0040] When the bill system receives the downlink message of the ticket exchange, it is forwarded to the bill system immediately; the bill system first performs internal logic processing, and when calling the associated accounting system, a token is taken from the global instruction token; if a token can be normally extracted, the associated accounting system is directly called for accounting processing, and the extracted token is returned to the instruction token.
[0041] S130, if the token extraction is not successful, the downlink message is pushed to the instruction message queue, and the instruction message queue is polled in real time by using an asynchronous task to buffer the downlink message stored in the instruction message queue.
[0042] The message queue, also referred to as a message middleware, can be used for transmitting messages between systems or within a system, and can be used for decoupling the system since the message middleware is not closely associated with the application. In the embodiment of the present application, the instruction message queue is used for storing the downlink messages that are not processed in real time, and the downlink messages that are not processed in real time are buffered.
[0043] If the token extraction is not successful, the downlink message is buffered by introducing an asynchronous task for synchronization. The downlink message is stored in the instruction message queue, and the instruction message queue is polled in real time by using an asynchronous task to buffer the downlink message stored in the instruction message queue.
[0044] The embodiment of the present application provides a downlink message flood processing method. The downlink message is received, and a token is extracted from a token. If the token extraction is successful, the downlink message is processed in real time by calling an associated account system, and the token is returned. If the token extraction is not successful, the downlink message is pushed to an instruction message queue, and the instruction message queue is polled in real time by using an asynchronous task to buffer the downlink message stored in the instruction message queue. According to the technical scheme of the embodiment of the present application, the instruction token and the instruction message queue are introduced for concurrent control, the downlink message is processed by combining real-time processing and buffering processing, and the processing efficiency of the downlink message is improved.
[0045] Embodiment two
[0046] Figure 4 A flowchart of a downlink message flood processing method provided by the embodiment two of the present application is provided. The embodiment of the present application is further optimized on the basis of the foregoing embodiment, and can be combined with each optional scheme in one or more of the foregoing embodiments. As shown in the flowchart of the downlink message flood processing method provided by the embodiment two of the present application, the method comprises the following steps. Figure 4
[0047] S410, receiving a downlink message and extracting a token from a token.
[0048] The ticket system receives a downlink message issued by a ticket exchange, and extracts a token from a token. The token is used to control the number of concurrent calls to an associated internal system. When the token can be normally obtained, the associated financial system can be called.
[0049] As an optional but non-limiting implementation manner, before the downlink message is received and the token is extracted from the token, the method further comprises the following steps A1-A2, but is not limited to the steps A1-A2.
[0050] Step A1: The message engine listens to the downlink message issued by the ticket exchange in real time.
[0051] Step A2: when the message engine listens to the downlink message, the downlink message is forwarded to the ticket system for internal logical processing of the downlink message by the ticket system.
[0052] Wherein, the exchange can refer to the construction and maintenance of the whole market ticket infrastructure, to provide ticket services for the whole market members. The message engine listens to the downlink message issued by the exchange in real time, and when the message engine listens to the downlink message issued by the exchange, the downlink message is forwarded to the ticket system for internal logical processing of the downlink message by the ticket system.
[0053] S420, if the token extraction is successful, the associated account system is called to process the downlink message in real time, and the token is returned.
[0054] S430, if the token extraction is not successful, the downlink message is pushed into the pre-constructed instruction message queue.
[0055] Wherein, if the token extraction fails, indicating that the number of concurrent calls to the associated account system has reached the upper limit value, the downlink message is pushed into the pre-constructed instruction message queue.
[0056] S440, the asynchronous task polls the instruction message queue in real time to determine whether there is a downlink message in the instruction message queue.
[0057] Wherein, the asynchronous task can refer to the task of buffering the downlink message by introducing the instruction message queue. The asynchronous task is started when the message engine listens to the downlink message issued by the exchange, to buffer the downlink message in the instruction message queue.
[0058] Wherein, see Figure 5 , the asynchronous task polls the instruction message queue in real time to determine whether there is a downlink message in the instruction message queue.
[0059] S450, when listening to the downlink message, the asynchronous task execution logic is entered to buffer the downlink message stored in the instruction message queue.
[0060] Wherein, when the asynchronous task listens to the downlink message, the asynchronous processing execution logic is entered, and the downlink message stored in the instruction message queue is buffered to improve the processing efficiency of the downlink message.
[0061] As an optional but not limited implementation manner, the entering of the asynchronous task execution logic to buffer the downlink message stored in the instruction message queue when listening to the downlink message includes but is not limited to steps B1-B3:
[0062] Step B1: when the downlink packet is monitored, the asynchronous task execution logic is entered, and the token is extracted from the instruction token.
[0063] Step B2: if the token extraction is successful, the associated accounting system is called to buffer the downlink packet in the instruction message queue, and the token is returned.
[0064] Step B3: if the token extraction is not successful, the token is extracted again after a preset time interval, and the associated accounting system is called to buffer the downlink packet in the instruction message queue after the token extraction is successful.
[0065] Wherein, when the asynchronous task real-time monitors the downlink packet, the asynchronous task execution logic is entered, and the token is extracted from the instruction token; if the token extraction is successful, the associated accounting system is called to buffer the downlink packet in the instruction message queue, and the token is returned; if the token extraction is not successful, the current polling is ended; the token is extracted again after a preset time interval, and the associated accounting system is called to buffer the downlink packet in the instruction message queue after the token extraction is successful.
[0066] Optionally, if the token extraction is not successful, it indicates that the number of concurrent calls to the associated accounting system has reached the upper limit value; the token is extracted again after a preset waiting time interval to determine whether the token extraction is successful, and the associated accounting system is called to buffer the downlink packet in the instruction message queue after the token extraction is successful.
[0067] Wherein, when the number of concurrent calls to the associated accounting system reaches the upper limit value, the token extraction will fail, at this time, a period of time needs to be waited, and after the associated accounting system is called, there will be an idle associated accounting system waiting for calling; after there is an idle associated accounting system, the token extraction is successful to call the associated accounting system to buffer the downlink packet in the instruction message queue.
[0068] The embodiment of the present application provides a downlink message flood processing method, which comprises the following steps: receiving a downlink message, and extracting a token from the token; if the token extraction is successful, calling an associated accounting system to perform real-time processing on the downlink message, and returning the token; if the token extraction is not successful, pushing the downlink message to a pre-constructed instruction message queue; an asynchronous task polling the instruction message queue in real time to determine whether there is a downlink message in the instruction message queue; when the downlink message is listened to, entering an asynchronous task execution logic to perform buffer processing on the downlink message stored in the instruction message queue. The technical scheme of the embodiment of the present application is suitable for the business characteristics and transaction characteristics of commercial bills, and a processing method suitable for third-party downlink message flood is designed, the real-time processing and the instruction message queue buffer processing are combined, the high efficiency of external message processing and the smooth high availability of inter-system calling are provided, and the high efficiency and high stability of message processing are realized.
[0069] Embodiment three
[0070] Figure 6 A structure schematic diagram of a downlink message flood processing device provided by the embodiment three of the present application is shown in the figure. Figure 6 As shown in the figure, the device comprises:
[0071] A downlink message receiving module 610 is configured to receive a downlink message, and extract a token from the token.
[0072] A downlink message real-time processing module 620 is configured to, if the token extraction is successful, call an associated accounting system to perform real-time processing on the downlink message, and return the token.
[0073] A downlink message buffer processing module 630 is configured to, if the token extraction is not successful, push the downlink message to an instruction message queue, and use an asynchronous task to poll the instruction message queue in real time to perform buffer processing on the downlink message stored in the instruction message queue.
[0074] Optionally, before receiving a downlink message and extracting a token from the token, the device further comprises a downlink message listening module, which is specifically configured to:
[0075] A message engine listens to a downlink message issued by a bill exchange in real time.
[0076] When the message engine listens to the downlink message, the downlink message is forwarded to a bill system to perform internal logic processing on the downlink message by using the bill system.
[0077] Optionally, the downlink message buffer processing module is specifically configured to:
[0078] If the token extraction is not successful, the downlink message is pushed to a pre-constructed instruction message queue.
[0079] The asynchronous task polls the instruction message queue in real time to determine whether there is a downlink message in the instruction message queue;
[0080] Upon listening to the downlink message, the asynchronous task execution logic is entered to buffer the downlink message stored in the instruction message queue.
[0081] Optionally, the downlink message buffering processing module is specifically configured to:
[0082] Upon listening to the downlink message, the asynchronous task execution logic is entered, and a token is extracted from the instruction token;
[0083] If the token extraction is successful, the associated accounting system is called to buffer the downlink message in the instruction message queue, and the token is returned;
[0084] If the token extraction is not successful, the token is extracted again after a preset time interval, and the associated accounting system is called to buffer the downlink message in the instruction message queue after the token extraction is successful.
[0085] Optionally, if the token extraction is not successful, it indicates that the number of concurrent calls to the associated accounting system has reached an upper limit value; the token is extracted again after a preset time interval to determine whether the token extraction is successful, and the associated accounting system is called to buffer the downlink message in the instruction message queue after the token extraction is successful.
[0086] Optionally, the asynchronous task is started when the message engine listens to the downlink message issued by the ticket exchange to buffer the downlink message in the instruction message queue.
[0087] The downlink message flood peak processing device provided in the embodiments of the present application can execute the downlink message flood peak processing method provided in any of the embodiments of the present application, has the corresponding functions and beneficial effects of executing the downlink message flood peak processing method, and the detailed process is described in the foregoing embodiments of the downlink message flood peak processing method.
[0088] Embodiment Four
[0089] Figure 7A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.
[0090] like Figure 7 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0091] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0092] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as downlink message flooding processing methods.
[0093] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program in accordance with embodiments of the present application. For example, embodiments of the present application include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for executing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication unit 19, or installed from the storage unit 18, or installed from the ROM 12. When the computer program is executed by the processor 11, the above-described functions defined in the methods of embodiments of the present application are performed.
[0094] In some embodiments, the downlink packet flood processing method can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded onto and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded onto the RAM 13 and executed by the processor 11, one or more steps of the downlink packet flood processing method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the downlink packet flood processing method by any other suitable means, such as by means of firmware.
[0095] Various implementations of the systems and techniques described above can be realized in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a complex programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
[0096] Computer programs used to implement the methods of the present application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the computer program, when executed by the processor of the machine, implements the functions / acts specified in the flowcharts and / or block diagrams. The computer program can be executed entirely on a machine, partially on a machine, partially on a machine and partially on a remote machine or entirely on a remote machine or server.
[0097] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of a machine-readable storage medium will include one or more lines of a program of instructions in a transitory signal, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0098] To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; 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 acoustic, speech, or tactile input.
[0099] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), blockchain network, and the Internet.
[0100] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.
[0101] It should be understood that the various forms of flow shown above can be used to reorder, add or delete steps. For example, each step described in the present application can be executed in parallel, sequentially or in a different order, as long as the desired results of the technical solutions of the present application can be achieved, which is not limited herein.
[0102] The above detailed description does not constitute a limitation on the scope of protection of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application shall be included in the scope of protection of the present application.
Claims
1. A method for processing a downlink packet flood, characterized in that, The method comprises: receiving a downlink message and extracting a token from the token; if the token extraction is successful, calling an associated accounting system to perform real-time processing on the downlink message and returning the token; if the token extraction is unsuccessful, pushing the downlink message to a command message queue and using an asynchronous task to perform real-time polling on the command message queue to perform buffer processing on the downlink message stored in the command message queue.
2. The method of claim 1, wherein, Before receiving the downlink message and extracting the token from the token, the method further comprises: the message engine real-time listens to the downlink message issued by the ticket exchange; when the message engine listens to the downlink message, the downlink message is forwarded to the ticket system to perform internal logic processing on the downlink message by using the ticket system.
3. The method of claim 1, wherein, If the token extraction is unsuccessful, the downlink message is pushed to a pre-constructed command message queue, and an asynchronous task is used to perform real-time polling on the command message queue to determine whether there is a downlink message in the command message queue. When the downlink message is listened to, the asynchronous task execution logic is entered to perform buffer processing on the downlink message stored in the command message queue. When the downlink message is listened to, the asynchronous task execution logic is entered, and the token is extracted from the token. If the token extraction is successful, the associated accounting system is called to perform buffer processing on the downlink message in the command message queue, and the token is returned.
4. The method of claim 3, wherein, If the token extraction is unsuccessful, the token is extracted again after a preset time interval, and the associated accounting system is called to perform buffer processing on the downlink message in the command message queue after the token extraction is successful. If the token extraction is unsuccessful, it indicates that the number of concurrent calls to the associated accounting system has reached an upper limit value; the token is extracted again after waiting for a preset time interval to determine whether the token extraction is successful, and buffer processing is performed on the downlink message in the command message queue by calling the associated accounting system after the token extraction is successful. The asynchronous task is started when the message engine listens to the downlink message issued by the ticket exchange to perform buffer processing on the downlink message in the command message queue. It comprises:
5. The method according to any one of claims 1 to 4, characterized in that, a downlink message receiving module for receiving a downlink message and extracting a token from the token; 6. The method of claim 1, wherein, a downlink message real-time processing module for calling an associated accounting system to perform real-time processing on the downlink message if the token extraction is successful, and returning the token; 7. A device for processing a downlink message flood, characterized in that, a downlink message buffer processing module for pushing the downlink message to a command message queue if the token extraction is unsuccessful, and using an asynchronous task to perform real-time polling on the command message queue to perform buffer processing on the downlink message stored in the command message queue. The electronic device comprises: at least one processor; and a memory connected in communication with the at least one processor; wherein 8. An electronic device, comprising: The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to perform the downlink packet flood processing method in any one of claims 1-6.
9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for enabling the processor to implement the downlink packet flood processing method in any one of claims 1-6 when executed.
10. A computer program product, characterised in that, The computer program product comprises a computer program which, when executed by a processor, implements the downlink packet flood processing method according to any one of claims 1-6.