CN116071177A - Method and device for distributing ticket to and from message based on message queue - Google Patents
Method and device for distributing ticket to and from message based on message queue Download PDFInfo
- Publication number
- CN116071177A CN116071177A CN202310102075.XA CN202310102075A CN116071177A CN 116071177 A CN116071177 A CN 116071177A CN 202310102075 A CN202310102075 A CN 202310102075A CN 116071177 A CN116071177 A CN 116071177A
- Authority
- CN
- China
- Prior art keywords
- message
- queue
- distribution
- processing
- ticket
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/128—Check-book balancing, updating or printing arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a method and a device for distributing an electric ticket to and from messages based on a message queue, wherein the method comprises the following steps: subscribing a message from a message sending queue and initializing setting, wherein the setting field of the message comprises a message type, a message table ID, delay processing time and repeated processing times; checking the system state according to the message type, if the checking is passed, performing the next step, otherwise, putting the message to be sent currently back to the corresponding queue; carrying out transaction flow identification according to the message type, and completing message assembly and signature processing; and pushing the message to be sent to a local queue in a short connection mode, and updating the state in a message table. The invention divides the message channel into the forward message and the backward message, and has higher processing efficiency compared with the message of a single channel, and simultaneously, the forward message establishes a special message queue according to the message type, so that the system can efficiently distribute the message, and the automatic message distribution based on the unified service scene is realized.
Description
Technical Field
The invention relates to the technical field of electric ticket messages, in particular to an electric ticket to and from message distribution method and device based on a message queue.
Background
In recent years, the construction of a bill service system re-plans a service architecture before bill cash, reconstructs a service function before bill cash, realizes bill cash issuing in an equal-division mode while supporting electric bill issuing in a traditional mode, realizes a bill 'change' function under the prior legal system framework, and provides important guarantee for better service entity economy and higher quality development of the bill.
After differentiated issuing of bill support and the like, the bill issuing requirements of all business departments are greatly stimulated, and meanwhile, the transaction amount of the secondary market is promoted, but the system message data amount is increased, and the limit situation can reach ten thousand TPS. Increasing amounts of data have resulted in lower data processing rates and higher costs; in a high concurrency scene, a message is often easy to lose, manual positioning and identification are needed, the usability of a system is reduced, the waiting time of queuing blocking is long, and the user experience is extremely unfriendly.
Disclosure of Invention
In view of the above problems, the invention provides a method and a device for distributing an electric ticket to and from a message queue, which achieve the effects of improving the message distribution efficiency and reducing the manual processing cost, support switch and retry configuration, and meet various personalized customization requirements.
In order to solve the technical problems, the invention adopts the following technical scheme: a method for distributing an electric ticket to and from message based on a message queue comprises the following steps: subscribing a message from a message sending queue and initializing setting, wherein the setting field of the message comprises a message type, a message table ID, delay processing time and repeated processing times; checking the system state according to the message type, if the checking is passed, performing the next step, otherwise, putting the message to be sent currently back to the corresponding queue; carrying out transaction flow identification according to the message type, and completing message assembly and signature processing; and pushing the message to be sent to a local queue in a short connection mode, and updating the state in a message table.
Preferably, the method further comprises: receiving a message from a local queue; outputting the incoming message to a log file and storing the incoming message in a message log table; according to the message distribution switch parameters and the message distribution rules, carrying out route distribution on the message; the message to be processed is stored in a message scheduling table, and is put into a designated queue for service logic processing; and judging whether the incoming service logic processing is successful, if so, deleting the message information corresponding to the message scheduling table, otherwise, updating the processing exception information and the exception processing times into the message scheduling table, and revising the queue to perform queuing processing again.
As a preferred scheme, the message sending queue comprises a ticket issuing registration queue, a prompt accepting queue, a prompt ticket collecting queue, a ticket withdrawing application queue and a public queue, and the messages with the service volume smaller than 50TPS are uniformly placed in the public queue according to the types and the service volumes of the messages and distributed to different queues.
Preferably, the message assembling and signing process is completed, including: and acquiring a message type and a message code according to a transaction component set by the transaction flow file, generating code service according to the message type and the message code, and completing the assembly of the message and signing.
Preferably, if the message log table data storage fails, the future message is stored in a single file form to a server abnormal message storage directory.
As a preferred scheme, the message distribution switch parameter is msgdispubuteflag, and when msgdispubuteflag=true, the message distribution is routed according to a pre-designated message distribution rule; the configuration information of the message distribution rule comprises: the method comprises the steps of obtaining client information according to an original application service type during specific distribution, judging whether to distribute, determining a distribution task type and a specific execution distribution method according to a transaction type, and storing a message meeting the rule into a local distribution temporary queue.
Preferably, the routing distribution according to a pre-designated message distribution rule includes: if the incoming message is a general forwarding message, acquiring client information of an accepting party from different fields according to the type of the original service application message in the general forwarding message, judging a gray list client according to the client information of the accepting party, and if the incoming message is a gray list client, carrying out message gray distribution; if the incoming message is a general determination message, a general reply message, a general withdrawal message or a general notification message, inquiring whether the original service message exists in a message log table according to the original message identification number and the message direction, if not, judging that the message is a gray list client, and distributing the message gray scale; if the message is the clearing failure message, searching a general determination message in a message log table according to an original message identification number and a message direction, searching whether the original service application message exists in the message log table, if not, judging that the message is a gray list client, and carrying out message gray distribution; if the general reply message is the clearing result notification message, judging whether the clearing result notification message is a message replied to the general reply message, if so, searching whether the general reply message exists in a message log table according to the original message identification number and the message direction, and if not, judging that the general reply message is a gray list client, and carrying out message gray distribution; if not, searching a ticket withdrawal application message, an information registration confirmation message, a payment prompting application message and a overdue payment prompting application message in a message log table according to the original message identification number and the message direction, and if not, judging that the client is a gray list client, and carrying out message gray distribution; if the system management message or the service check message is the system management message or the service check message, unified processing is carried out, and gray scale is not carried out and the system management message or the service check message is directly distributed.
As a preferred scheme, the signing and analyzing process is performed on the incoming message, including: and carrying out asymmetric signature verification according to the public key provided by the server, and carrying out deserialization by adopting the serizable to complete message analysis.
The invention also provides a ticket to/from message distribution device based on the message queue, comprising: the subscription module is used for subscribing the message from the message sending queue and initializing the setting, wherein the setting field of the message comprises a message type, a message table ID, delay processing time and repeated processing times; the checking module is used for checking the system state according to the message type, if the system state is checked to be passed, the next step is carried out, otherwise, the message to be sent currently is put back to the corresponding queue; the assembly and signing module is used for carrying out transaction flow identification according to the message type and completing message assembly and signing processing; and the pushing updating module is used for pushing the message to be sent to the local queue in a short connection mode and updating the state in the message table.
Preferably, the system also comprises a receiving module, which is used for receiving the message from the local queue; the output and storage module is used for outputting the incoming message to a log file and storing the incoming message in a message log table; the route distribution module is used for carrying out route distribution on the incoming message according to the message distribution switch parameters and the message distribution rules; the logic processing module is used for carrying out signature verification and analysis processing on the incoming message, storing the incoming message to be processed into a message scheduling table, and putting the message into a designated queue for carrying out business logic processing; and the result judging module is used for judging whether the incoming call service logic processing is successful, if so, deleting the message information corresponding to the message scheduling table, otherwise, updating the processing exception information and the exception processing times into the message scheduling table, and revising the queue to perform queuing processing again.
Compared with the prior art, the invention has the beneficial effects that: the message channels are divided into the forward message and the backward message, so that the message processing efficiency is higher compared with that of a single channel, and meanwhile, the forward message and the backward message establish a special message queue according to the message type, so that the system can efficiently distribute the messages, and the unified service scene-based automatic message distribution is realized. Under the high concurrency scene, the method can meet the condition that the message queue cannot block the exception, support the re-calling queuing processing of the message processing exception, and ensure that the message cannot be lost.
Drawings
The disclosure of the present invention is described with reference to the accompanying drawings. It is to be understood that the drawings are designed solely for the purposes of illustration and not as a definition of the limits of the invention. In the drawings, like reference numerals are used to refer to like parts. Wherein:
FIG. 1 is a schematic diagram of a report processing flow according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a processing flow according to an embodiment of the invention.
Detailed Description
It is to be understood that, according to the technical solution of the present invention, those skilled in the art may propose various alternative structural modes and implementation modes without changing the true spirit of the present invention. Accordingly, the following detailed description and drawings are merely illustrative of the invention and are not intended to be exhaustive or to limit the invention to the precise form disclosed.
The invention provides a method for distributing an electric ticket to and from messages based on a message queue, which is divided into a forward message sending process and a forward message receiving process.
Referring to fig. 1, the above-mentioned report sending process flow includes the following steps:
1) Subscribing to the message from the message sending queue and initializing the setting.
The set fields of the message include message type, message table ID, delay processing time and repeated processing times. The following table shows:
when the message is sent, a distribution record is inserted into the database, and the state is initialized. The delay processing time can be set to customize message queuing time, so that the transmission of important class messages is preferentially ensured, and non-business class messages can be properly queued for execution, so that business processing efficiency is ensured. The repeated processing times can ensure that the message is not lost, the repeated processing failure is directly converted into a failure message, the manual execution is completed, and the repeated transmission is forbidden until the feedback result is not received.
And the ticket front-end service system (ECDP) uses a message queue monitoring mode to subscribe to a corresponding message from a message sending queue of the corresponding ECDS bill system. The message sending queue comprises a ticket issuing registration queue, a prompt accepting queue, a prompt ticket collecting queue, a ticket withdrawing application queue and a public queue, wherein the message sending queue comprises the ticket issuing registration queue, the prompt accepting queue, the ticket withdrawing application queue and the public queue, the message sending queue is distributed to different queues according to the type and the traffic of the message, and the message with the traffic less than 50TPS is uniformly placed in the public queue XXXX.
2) And (3) checking the system state according to the message type, if the system state is checked to pass, performing the next step, otherwise, if the message is not allowed to be sent under the current system state, putting the message to be sent back to the corresponding queue, and performing queuing treatment. For example: the current system state comprises a business state and a non-business state, wherein the business state can send business application type messages, and otherwise, the business application type messages are not allowed to be sent.
3) And carrying out transaction flow identification according to the message type, and completing message assembly and signing processing.
Specifically, the message assembly and signing process is completed, including: and acquiring a message type and a message code according to a transaction component set by the transaction flow file, generating code service according to the message type and the message code, and completing the assembly of the message and signing.
For example: the client initiates a transaction application message-002; the transaction component adopts a factory mode, firstly, a message type (transaction application) and a message code (002) are obtained, 002 ServiceIII code service is generated according to the message type and the message code, and the application message is assembled and signed; push the message to the local queue (ecds. Send. 002).
4) And pushing the message to be sent to a local queue in a short connection mode, and updating the state in a message table. The system judges the IBM MQ local sending queue according to the message type, and puts the assembled message into the corresponding queue.
Referring to fig. 2, the above-mentioned incoming report receiving process flow includes the following steps:
1) A message is received from the local queue. The ticket front end service system is responsible for interfacing to the IBM MQ and receiving ECDS messages from local queues xxxxxxxxxxx_5 and xxxxxxxxxxx_6.
The setting fields of the incoming message include message type, message table ID, message identification number, original message ID, delay processing time and message receiving time. The following table shows:
2) And outputting the message to a log file, and storing the message in a message log table.
The ticket front-end service system outputs the complete message to the log file, and then stores the message to the message log table MSG_MESSAGELOG table. If the message log table data storage fails, storing the future message into a server abnormal message storage directory in a single file form, and naming the file format: errMsg_yyyyMMddHHmmSSS.txt.
3) And carrying out route distribution on the incoming message according to the message distribution switch parameters and the message distribution rules.
The message distribution switch parameter is msgdispubuteflag, and the ticket front-end service system judges the message distribution switch parameter, and when msgdispubuteflag=true, the message distribution is routed according to a pre-designated message distribution rule.
The configuration information of the message distribution rule comprises: the method comprises the steps of obtaining client information according to an original application service type during specific distribution, judging whether to distribute, determining a distribution task type and a specific execution distribution method according to a transaction type, and storing a message meeting the rule into a local distribution temporary queue. The ticket pre-service system distributes the incoming message in XXXXXXXX_5 to the XXXXXXXX_51 queue by default, and distributes the incoming message in XXXXXXXX_6 to the XXXXXXXXXX_61 queue.
In the embodiment of the invention, the message types comprise the following categories:
1. general information class: general reply message-031; general revocation message-032; general determination message-033; general forwarding message-034; universal failure reply message-035; general result notification message-036.
2. Transaction application class: a ticket issuing registration message-002; prompting acceptance message-003; prompting a ticket collecting message-010; removing ticket application messages-011; information registration confirmation message-012; transferring a back book message-017; prompting a payment application message-020; overdue prompt payment application message-021, etc.
3. System management class: the total number of messages is 16, namely 051-067.
4. Service check class: the total number of messages is 9, namely 071-079.
In the embodiment of the invention, the local queue types comprise the following categories:
1. name of the report queue: ecds.send.001-ticket check-in queue; ECDS.SEND.002-hint acceptance queue; ECDS.SEND.003-prompt ticket collection queue; ecds. Send.004 drop-out application queue; ecds.
2. The name of the incoming report queue: ecds. Receive.031-generic reply queue; ecds. Receive. 032-generic revocation queue; ecds.receive.033-generic acknowledgement queue; ecds.receive.034-generic forwarding queue; ecds. Receive. Comm-other generic queues.
In the embodiment of the invention, the local distribution temporary queue generation rule is as follows: name of the report queue: the XXXXXXXX_1 is generated incrementally, and the XXXXXX is the bank institution code; the name of the incoming report queue: XXXXXXXX_11 corresponds to the reporting temporary queue XXXXXXXX_1, and the analog XXXXXXXX_21 corresponds to the reporting queue XXXXXXXX_2.
The routing distribution is performed according to a pre-designated message distribution rule, which comprises the following steps:
if the incoming message is a general forwarding message, acquiring client information of an accepting party from different fields according to the type of the original service application message in the general forwarding message, judging a gray list client according to the client information of the accepting party, and if the incoming message is a gray list client, carrying out message gray distribution; if the client is a white list client, the client is directly put into a queue for distribution.
If the incoming message is a general determination message, a general reply message, a general withdrawal message or a general notification message, inquiring whether the original service message exists in a message log table according to the original message identification number and the message direction, if not, judging that the message is a gray list client, and distributing the message gray scale;
if the message is the clearing failure message, searching a general determination message in a message log table according to an original message identification number and a message direction, searching whether the original service application message exists in the message log table, if not, judging that the message is a gray list client, and carrying out message gray distribution;
if the general reply message is the clearing result notification message, judging whether the clearing result notification message is a message replied to the general reply message, if so, searching whether the general reply message exists in a message log table according to the original message identification number and the message direction, and if not, judging that the general reply message is a gray list client, and carrying out message gray distribution; if not, searching a ticket withdrawal application message, an information registration confirmation message, a payment prompting application message and a overdue payment prompting application message in a message log table according to the original message identification number and the message direction, and if not, judging that the client is a gray list client, and carrying out message gray distribution;
if the system management message or the service check message is the system management message or the service check message, unified processing is carried out, and gray scale is not carried out and the system management message or the service check message is directly distributed.
4) And carrying out verification and analysis processing on the incoming message, storing the incoming message to be processed into a message scheduling table, and putting the message into a designated queue for carrying out service logic processing. The ticket front-end service system acquires the incoming call service processing information from the appointed receiving queue, and acquires the corresponding service processing service according to the type of the information to carry out service logic processing.
The method for verifying and analyzing the incoming message comprises the following steps: and carrying out asymmetric signature verification according to the public key provided by the server, and carrying out deserialization by adopting the serizable to complete message analysis.
After the analysis of the message is completed, the ECDP firstly stores the message to be processed into a message scheduling table [ MSG_ RECDISPATCH ], puts the message needing to be processed by service logic into a specified queue, and transmits the message to ECDM service for service logic processing. The incoming service processing message fields are: msgType message type, msgtab message table ID, msgtno message identification number, creDtTm message reception time, delay time delay processing time.
5) Judging whether the service logic processing is successful or not, if so, deleting the message information corresponding to the message scheduling table [ MSG_ RECDISPATCH ], otherwise, updating the processing exception information and the exception processing times into the message scheduling table, and revising the queue for queuing processing again.
The invention provides a message queue-based electric ticket incoming and outgoing message distribution method, when receiving messages, a message queue mode is used for scheduling a plurality of incoming message service processing services, message analysis logic is adjusted to support multi-thread multi-service processing, the incoming message analysis processing capacity is improved, firstly, an incoming message record is inserted into a database, the state is set as initialization, and the set fields comprise message types, message table ids, message mark numbers, original message ids, original message mark numbers, delay processing time and message receiving time. And acquiring the Service of the business processing Service corresponding to the message according to the message type to perform specific logic processing. The Service judges whether the message needs queuing. If queuing is not needed, the business logic processing is directly carried out. If queuing is needed (the message has a pre-message which is not processed), the service logic processing is not performed, and the message execution message is directly stored in the out-of-order queuing schedule in the form of JSON data. And finally updating the message distribution record state, wherein the modification state field is the processing completion, and the message distribution times field is the number of warehouse entry.
The invention also provides a ticket to/from message distribution device based on the message queue, comprising:
the subscription module is used for subscribing the message from the message sending queue and initializing the setting, and the setting field of the message comprises the message type, the message table ID, the delay processing time and the repeated processing times;
the checking module is used for checking the system state according to the message type, if the system state is checked to be passed, the next step is carried out, otherwise, the message to be sent currently is put back to the corresponding queue;
the assembly and signing module is used for carrying out transaction flow identification according to the message type and completing message assembly and signing processing; and the pushing updating module is used for pushing the message to be sent to the local queue in a short connection mode and updating the state in the message table.
The receiving module is used for receiving the incoming message from the local queue;
the output and storage module is used for outputting the message to a log file and storing the message in a message log table;
the route distribution module is used for carrying out route distribution on the incoming messages according to the message distribution switch parameters and the message distribution rules;
the logic processing module is used for carrying out signature verification and analysis processing on the incoming message, storing the incoming message to be processed into a message scheduling table, and putting the message into a specified queue for carrying out business logic processing;
and the result judging module is used for judging whether the service logic processing is successful or not, if so, deleting the message information corresponding to the message scheduling table, otherwise, updating the processing exception information and the exception processing times into the message scheduling table, and revising the queue to perform queuing processing again.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In summary, the beneficial effects of the invention include: the message channels are divided into the forward message and the backward message, so that the message processing efficiency is higher compared with that of a single channel, and meanwhile, the forward message and the backward message establish a special message queue according to the message type, so that the system can efficiently distribute the messages, and the unified service scene-based automatic message distribution is realized. Under the high concurrency scene, the method can meet the condition that the message queue cannot block the exception, support the re-calling queuing processing of the message processing exception, and ensure that the message cannot be lost.
The invention has the advantages that: the system sends a message, if the network packet is lost, the communication interruption of the server is not received, and the system supports retransmission; (2) capable of feeding back error information: after the server side analyzes the message, the system receives error feedback and analyzes and displays the error feedback to the user, so that the problem can be conveniently positioned and processed; (3) performance considerations: the system sends a message, does not receive result feedback, does not allow retransmission operation, and supports retry and retransmission.
It should be appreciated that the integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The technical scope of the present invention is not limited to the above description, and those skilled in the art may make various changes and modifications to the above-described embodiments without departing from the technical spirit of the present invention, and these changes and modifications should be included in the scope of the present invention.
Claims (10)
1. The method for distributing the ticket to and from messages based on the message queue is characterized by comprising the following steps:
subscribing a message from a message sending queue and initializing setting, wherein the setting field of the message comprises a message type, a message table ID, delay processing time and repeated processing times;
checking the system state according to the message type, if the checking is passed, performing the next step, otherwise, putting the message to be sent currently back to the corresponding queue;
carrying out transaction flow identification according to the message type, and completing message assembly and signature processing;
and pushing the message to be sent to a local queue in a short connection mode, and updating the state in a message table.
2. The message queue-based ticket transaction message distribution method of claim 1, further comprising:
receiving a message from a local queue;
outputting the incoming message to a log file and storing the incoming message in a message log table;
according to the message distribution switch parameters and the message distribution rules, carrying out route distribution on the message;
the message to be processed is stored in a message scheduling table, and is put into a designated queue for service logic processing;
and judging whether the incoming service logic processing is successful, if so, deleting the message information corresponding to the message scheduling table, otherwise, updating the processing exception information and the exception processing times into the message scheduling table, and revising the queue to perform queuing processing again.
3. The message queue-based electric ticket business message distribution method of claim 1, wherein the message transmission queues comprise a ticket issuing registration queue, a prompt acceptance queue, a prompt ticket collecting queue, a ticket withdrawing application queue and a public queue, and messages with the traffic less than 50TPS are uniformly placed in the public queue according to the types and the traffic of the messages and distributed to different queues.
4. The message queue-based ticket transaction message distribution method as claimed in claim 1, wherein the completion message assembly and signing process comprises: and acquiring a message type and a message code according to a transaction component set by the transaction flow file, generating code service according to the message type and the message code, and completing the assembly of the message and signing.
5. The message queue-based ticket transaction message distribution method as claimed in claim 2, wherein if the message log table data storage fails, the future message is stored in a single file form to a server abnormal message storage directory.
6. The message queue-based ticket to and from message distribution method according to claim 2, wherein the message distribution switch parameter is msgdtributedflag, and when msgdtributedflag=true, the message distribution is routed according to a pre-designated message distribution rule;
the configuration information of the message distribution rule comprises: the method comprises the steps of obtaining client information according to an original application service type during specific distribution, judging whether to distribute, determining a distribution task type and a specific execution distribution method according to a transaction type, and storing a message meeting the rule into a local distribution temporary queue.
7. The message queue-based ticket transaction message distribution method as claimed in claim 6, wherein the routing distribution is performed according to a pre-specified message distribution rule, comprising:
if the incoming message is a general forwarding message, acquiring client information of an accepting party from different fields according to the type of the original service application message in the general forwarding message, judging a gray list client according to the client information of the accepting party, and if the incoming message is a gray list client, carrying out message gray distribution;
if the incoming message is a general determination message, a general reply message, a general withdrawal message or a general notification message, inquiring whether the original service message exists in a message log table according to the original message identification number and the message direction, if not, judging that the message is a gray list client, and distributing the message gray scale;
if the message is the clearing failure message, searching a general determination message in a message log table according to an original message identification number and a message direction, searching whether the original service application message exists in the message log table, if not, judging that the message is a gray list client, and carrying out message gray distribution;
if the general reply message is the clearing result notification message, judging whether the clearing result notification message is a message replied to the general reply message, if so, searching whether the general reply message exists in a message log table according to the original message identification number and the message direction, and if not, judging that the general reply message is a gray list client, and carrying out message gray distribution; if not, searching a ticket withdrawal application message, an information registration confirmation message, a payment prompting application message and a overdue payment prompting application message in a message log table according to the original message identification number and the message direction, and if not, judging that the client is a gray list client, and carrying out message gray distribution;
if the system management message or the service check message is the system management message or the service check message, unified processing is carried out, and gray scale is not carried out and the system management message or the service check message is directly distributed.
8. The message queue-based ticket transaction message distribution method as claimed in claim 2, wherein the step of performing signature verification and analysis processing on the transaction message comprises the steps of: and carrying out asymmetric signature verification according to the public key provided by the server, and carrying out deserialization by adopting the serizable to complete message analysis.
9. An electronic ticket to and from message distribution device based on a message queue, comprising:
the subscription module is used for subscribing the message from the message sending queue and initializing the setting, wherein the setting field of the message comprises a message type, a message table ID, delay processing time and repeated processing times;
the checking module is used for checking the system state according to the message type, if the system state is checked to be passed, the next step is carried out, otherwise, the message to be sent currently is put back to the corresponding queue;
the assembly and signing module is used for carrying out transaction flow identification according to the message type and completing message assembly and signing processing;
and the pushing updating module is used for pushing the message to be sent to the local queue in a short connection mode and updating the state in the message table.
10. The message queue-based ticket to and from message distribution apparatus of claim 9, further comprising:
the receiving module is used for receiving the message from the local queue;
the output and storage module is used for outputting the incoming message to a log file and storing the incoming message in a message log table;
the route distribution module is used for carrying out route distribution on the incoming message according to the message distribution switch parameters and the message distribution rules;
the logic processing module is used for carrying out signature verification and analysis processing on the incoming message, storing the incoming message to be processed into a message scheduling table, and putting the message into a designated queue for carrying out business logic processing;
and the result judging module is used for judging whether the incoming call service logic processing is successful, if so, deleting the message information corresponding to the message scheduling table, otherwise, updating the processing exception information and the exception processing times into the message scheduling table, and revising the queue to perform queuing processing again.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310102075.XA CN116071177A (en) | 2023-02-03 | 2023-02-03 | Method and device for distributing ticket to and from message based on message queue |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310102075.XA CN116071177A (en) | 2023-02-03 | 2023-02-03 | Method and device for distributing ticket to and from message based on message queue |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116071177A true CN116071177A (en) | 2023-05-05 |
Family
ID=86176676
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310102075.XA Pending CN116071177A (en) | 2023-02-03 | 2023-02-03 | Method and device for distributing ticket to and from message based on message queue |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116071177A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116910330A (en) * | 2023-09-12 | 2023-10-20 | 湖南科研云信息科技有限公司 | Financial archive management method, system, electronic equipment and storage medium |
-
2023
- 2023-02-03 CN CN202310102075.XA patent/CN116071177A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116910330A (en) * | 2023-09-12 | 2023-10-20 | 湖南科研云信息科技有限公司 | Financial archive management method, system, electronic equipment and storage medium |
| CN116910330B (en) * | 2023-09-12 | 2023-12-05 | 湖南科研云信息科技有限公司 | Financial archive management method, system, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2395114C2 (en) | Methods and systems of messages exchange with mobile devices | |
| US6996409B2 (en) | Multi-party concurrence through short message service exchanges | |
| US10873555B2 (en) | General purpose messaging | |
| CN1148689C (en) | Transaction support system and information terminal system connected with the same | |
| CN111866769B (en) | Message sending method, device, server and medium | |
| US20110276483A1 (en) | Method and device for depositing checks | |
| CA2584143A1 (en) | A method and system for regulating electronic mail | |
| CN111030784A (en) | Information synchronization method and device | |
| WO2007136872A2 (en) | Systems and methods for adding credit to a wireless telecommunications account | |
| US20060086798A1 (en) | Deferred email message system and service | |
| US20080261635A1 (en) | Mobile messaging system | |
| US7590701B2 (en) | Apparatus and method for generating alert messages in a message exchange network | |
| CN113259496B (en) | Bank-enterprise direct connection system and method based on financial service | |
| CN116071177A (en) | Method and device for distributing ticket to and from message based on message queue | |
| CN101073237B (en) | Method for delivering multimedia files | |
| US9209994B2 (en) | System and method for enhanced application server | |
| CN113395315B (en) | Message broadcasting method, cloud loudspeaker box and cloud pushing platform | |
| CN112887193A (en) | Message sending method, system, terminal and storage medium | |
| CN112862435A (en) | Browser-based converged office method and system | |
| CN100558188C (en) | Message processing device, system and method | |
| US7881735B2 (en) | Messaging gateway and method | |
| CN113992352A (en) | Message pushing method and device, electronic equipment and storage medium | |
| CN101820577A (en) | Method and device for presenting individual ring-back tone | |
| CN113852627B (en) | Extensible payment message processing method and device and electronic equipment | |
| CN113362043B (en) | System and method for realizing cooperation of resident identification card management business in trans-province mode |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |