CN112561611A - Electronic bill multi-channel delivery method and system - Google Patents
Electronic bill multi-channel delivery method and system Download PDFInfo
- Publication number
- CN112561611A CN112561611A CN202011564059.5A CN202011564059A CN112561611A CN 112561611 A CN112561611 A CN 112561611A CN 202011564059 A CN202011564059 A CN 202011564059A CN 112561611 A CN112561611 A CN 112561611A
- Authority
- CN
- China
- Prior art keywords
- delivery
- bill
- request
- core engine
- channel
- 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.)
- Granted
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
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
Abstract
The invention relates to an electronic bill multi-channel delivery method, which comprises the following steps: s1, establishing a configuration database, wherein the configuration database stores delivery channel information configured by an invoicing unit; s2, the service request party sends a delivery request to the core engine, wherein the delivery request comprises bill summary information, billing units and receiver information; s3, the core engine processes the delivery request and calls a delivery module: the core engine inquires delivery channel information of the billing unit in a configuration database according to the billing unit; the core engine sends bill summary information, receiver information and delivery channel information to the delivery module; and S4, the delivery module asynchronously carries out the delivery with the ticket and the delivery without the ticket.
Description
Technical Field
The invention relates to an electronic bill multi-channel delivery system, and belongs to the field of electronic bills.
Background
Paper bills are gradually replaced by electronic bills (the electronic bills comprise financial electronic bills and tax electronic invoices), and the current flow of making and delivering the electronic bills is as follows: enterprises and individuals apply for ticketing from financial ticketing systems of all places; since the financial billing system requires a certain time for billing, businesses and individuals need to manually reserve contact means such as mailboxes, telephones and the like in the financial billing system to complete delivery of electronic bills (for example, 51 invoice platform). The mode delivery channel is single, mistakes are easy to make, electronic bills cannot be automatically delivered in batches, user experience is poor, and the mode delivery channel is not beneficial to implementation of the electronic bills.
Patent publication No. CN201811582535.9, an electronic invoice delivery method and system, discloses the following steps: receiving consumption information; generating a two-dimensional code according to the consumption information and a preset rule; displaying the two-dimension code to the payer according to a preset display mode, and uploading third-party software account information of the payer and consumption information corresponding to the two-dimension code to a cloud server through scanning of the payer by using pre-specified third-party software; displaying the consumption information on the third-party software interface, receiving invoice information input by a payer, and uploading the invoice information to a cloud server; the cloud server completes electronic invoice issuing according to the consumption information and the invoice information and preset rules, and delivers the electronic invoice to an account of third-party software of the payer through the third-party software account information of the payer; the method and the system save the complicated process of electronic invoice delivery and solve the problems of trouble delivery and volatile failure of the electronic invoice.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides an electronic bill multi-channel delivery system, which provides various delivery channels, meets the requirement of diversity of a receiver, divides a delivery flow into a ticket-free delivery process and a ticket-containing delivery process, asynchronously carries out the ticket-containing delivery process and the ticket-free delivery process, and improves the user experience because the receiver receives the ticket-free delivery information in real time and then receives a plate-type file.
The technical scheme of the invention is as follows:
the first technical scheme is as follows:
an electronic bill multi-channel delivery method comprises the following steps:
s1, establishing a configuration database, wherein the configuration database stores delivery channel information configured by an invoicing unit;
s2, the service requester sends a delivery request to the core engine, wherein the delivery request comprises bill summary information, an ID of a billing unit and information of a receiver;
s3, the core engine processes the delivery request and calls a delivery module: the core engine inquires delivery channel information of the billing unit in a configuration database according to the ID of the billing unit; the core engine sends bill summary information, receiver information and delivery channel information to the delivery module;
s4, the delivery module asynchronously carries out the delivery with the ticket and the delivery without the ticket:
the delivery module carries out ticketless delivery: the delivery module converts the bill summary information and the receiver information into parameters required by a delivery channel and encrypts the parameters; the delivery module sends the encrypted parameters and the bill display link to a receiver through a delivery channel;
the delivery module judges whether the bill delivery is carried out or not, if the bill delivery is carried out, the core engine downloads the plate-type file of the bill and sends the plate-type file to the delivery module; the delivery module sends the plate file to the recipient through a delivery channel.
Furthermore, the delivery modules are multiple and are respectively deployed on different servers;
establishing a message queue;
the core engine checks the received delivery request, adds the delivery request passing the check into the message queue and sends a receiving state notification to a delivery request sender;
and the core engine takes the delivery request from the message queue for processing and polls and calls the plurality of delivery modules.
Further, the delivery request also comprises a delivery request ID and a plurality of request parameters for describing the ticket condition;
the specific steps for verifying the delivery request are as follows:
performing idempotent verification on the delivery request ID by the core engine to screen out repeated delivery requests;
the core engine performs identity verification on the request parameters to verify the validity of the delivery request.
Further, the delivery request further includes a ticket ID;
the core engine processes the delivery request and judges whether the bill is repeated according to the bill ID, if so, the processing is stopped and the delivery request is abandoned.
Further, determining a plurality of steps as compensation nodes;
setting a compensation table, wherein the compensation table comprises each compensation node ID and data related to each compensation node;
if a certain compensation node is abnormal, the core engine records the abnormal time and executes the compensation node again at regular time; and locking the data related to the compensation node when the compensation node is executed again until the compensation node is executed.
Further, the data slices in the configuration database are stored on different servers.
The second technical scheme is as follows:
an electronic bill multi-channel delivery system comprises a core engine, a configuration database and a delivery module, wherein delivery channel information configured by an invoicing unit is stored in the configuration database;
the service requester sends the delivery request to a core engine, wherein the delivery request comprises bill summary information, an ID of a billing unit and information of a receiver;
the core engine is in communication connection with the delivery module and is used for inquiring the delivery channel information of the billing unit in a configuration database according to the ID of the billing unit and sending the bill summary information, the receiver information and the delivery channel information to the delivery module;
the delivery module is used for asynchronously carrying out the delivery with the ticket and the delivery without the ticket:
the delivery module carries out ticketless delivery: the delivery module converts the bill summary information and the receiver information into parameters required by a delivery channel and encrypts the parameters; the delivery module sends the encrypted parameters to a receiver through a delivery channel;
the delivery module judges whether the bill delivery is carried out or not, if the bill delivery is carried out, the core engine downloads the plate-type file of the bill and sends the plate-type file to a delivery service; the delivery module delivers the plate document to the recipient through a delivery channel.
Furthermore, the delivery modules are multiple and are respectively deployed on different servers;
establishing a message queue;
the core engine checks the received delivery request, adds the delivery request passing the check into the message queue and sends a receiving state notification to a delivery request sender;
and the core engine takes the delivery request from the message queue for processing and polls and calls the plurality of delivery modules.
Further, the delivery request also comprises a delivery request ID, a bill ID and a plurality of request parameters for describing the bill condition;
the delivery request is verified by the following steps: performing idempotent verification on the delivery request ID by the core engine to screen out repeated delivery requests; the core engine carries out identity verification on the plurality of request parameters so as to verify the validity of the delivery request;
and filtering the repeated bills according to the bill IDs, wherein the steps are as follows: the core engine processes the delivery request and judges whether the bill is repeated according to the bill ID, if so, the processing is stopped and the delivery request is abandoned.
Further, determining a plurality of steps as compensation nodes;
setting a compensation table, wherein the compensation table comprises each compensation node ID and data related to each compensation node;
if one compensation node is abnormal, the core engine records the abnormal time in the compensation table and executes the compensation node again at regular time; and when the compensation node is executed again, locking the data related to the compensation node according to the compensation table until the compensation node is executed.
The invention has the following beneficial effects:
1. a plurality of delivery channels are provided to meet the requirement of diversity of the receiver;
2. the delivery process is divided into ticketless delivery and ticketed delivery, the ticketed delivery and the ticketless delivery are asynchronously carried out, and a receiver receives the ticketless delivery information in real time and then receives the plate-type file, so that the user experience is improved;
3. the message queue is used for storing the delivery request, and the core engine can immediately return a success failure state to the service requester after receiving the delivery request, so that the response efficiency of the core engine is improved; under the condition of simultaneously receiving a large number of delivery requests, the plurality of deployed delivery modules concurrently process the plurality of delivery requests, so that the delivery efficiency and stability are improved;
4. a timing compensation mechanism is set, so that a receiver and a billing unit can know which step a certain ticket is specifically clamped, and the user experience is further improved;
5. through data fragmentation, the retrieval speed is accelerated, and the downtime influence is reduced.
Drawings
FIG. 1 is a flow chart of the present invention;
FIG. 2 is a schematic diagram of data exchange;
FIG. 3 is a flow chart of a check delivery request;
FIG. 4 is a flow chart of the process of screening out duplicate bills;
fig. 5 is a schematic diagram of a timing compensation mechanism.
Detailed Description
The invention is described in detail below with reference to the figures and the specific embodiments.
Example one
An electronic bill multi-channel delivery method comprises the following steps:
s1, establishing a configuration database, wherein the configuration database stores delivery channel information configured by an invoicing unit;
s2, the service requester sends a delivery request to the core engine, wherein the delivery request comprises bill summary information, an ID of a billing unit and information of a receiver;
s3, the core engine processes the delivery request and calls a delivery module: the core engine inquires delivery channel information of the billing unit in a configuration database according to the ID of the billing unit; the core engine sends bill summary information, receiver information and delivery channel information to the delivery module;
s4, the delivery module asynchronously carries out the delivery with the ticket and the delivery without the ticket:
the delivery module carries out ticketless delivery: the delivery module converts the bill summary information and the receiver information into parameters required by a delivery channel and conducts RSA encryption on the parameters; the delivery module sends the encrypted parameters and the bill display link to a receiver through a delivery channel; (in this embodiment, the core engine obtains the bill showing link from the bill service platform and sends the showing link to the delivery module together with the bill summary information, the bill showing link, the receiver information and the delivery channel information.)
The delivery module judges whether the bill delivery is carried out, if the bill delivery is carried out, the core engine downloads the plate-type file of the bill and sends the plate-type file to the delivery module (in the embodiment, the core engine downloads the plate-type file of the bill from each local bill service platform); the delivery module sends the plate file to the recipient through a delivery channel.
The delivery channel is WeChat card package, Payment treasures invoice manager, short message, mail, Unionpay card package, etc. Different delivery channels require different parameters, such as payment treasures invoicing butler needing to pay treasures id to push to the user. The user can select whether to make the delivery with the ticket or without the ticket. In this embodiment, the delivery module determines whether to deliver the ticketed service according to the type of the delivery channel, for example, the short message, the treasury payment invoice manager, and the union pay card package are non-ticketed delivery channels; the mail is a ticketed delivery channel.
The beneficial effect of this embodiment lies in:
1. a plurality of delivery channels are provided to meet the requirement of diversity of the receiver;
2. the delivery process is divided into ticketless delivery and ticketed delivery, the ticketed delivery and the ticketless delivery are carried out asynchronously, and a receiver receives the ticketless delivery information in real time and then receives the plate-type file, so that the user experience is improved.
Example two
In this embodiment, the message queue and the core engine are respectively deployed in different servers, and the plurality of delivery modules are respectively deployed on different servers.
Referring to fig. 3 and 4, the core engine checks the received delivery request, and the specific steps for checking the delivery request are as follows:
performing idempotent verification on the delivery request ID by the core engine to screen out repeated delivery requests;
the core engine performs identity verification on a plurality of request parameters (such as bill types, bill conditions and the like) to verify the validity of the delivery request.
In this implementation, the billing entity is provided with a key, which the core engine also maintains. And the billing unit carries out ascending sequencing on the plurality of request parameters, carries out first encryption by using the key, and carries out second encryption by using the MD5 algorithm to obtain a first character string. The billing unit sends a delivery request containing the character string and a plurality of request parameters. The core engine inquires a key of the unit according to the ID of the billing unit, firstly encrypts a plurality of request parameters in the delivery request by using the key, and secondly encrypts by using an MD5 algorithm to obtain a second character string; and comparing the first character string with the second character string, and if the comparison result is consistent, passing the identity verification.
And the core engine adds the delivery request passing the verification into a message queue and sends a receiving state notice to a delivery request sender.
The core engine takes out the delivery request from the message queue for processing: the core engine processes the delivery request and judges whether the bill is repeated according to the bill ID, if so, the processing is stopped and the delivery request is abandoned. The core engine then polls for multiple delivery modules.
The method has the advantages that the delivery request is stored by using the message queue, and the core engine can immediately return the receiving state notification to the service requester after receiving the delivery request, so that the response efficiency of the core engine is improved; under the condition of simultaneously receiving a large number of delivery requests, the delivery module concurrently processes a plurality of delivery requests, and the delivery efficiency and stability are improved.
EXAMPLE III
In this embodiment, the billing service requester is a billing system;
as shown in fig. 2, the applicant performs payment and billing operations in the billing system. The billing system applies for ticket making to various local ticket service platforms and sends delivery requests to the delivery system.
A core engine in a delivery system receives a delivery request; the core engine checks the delivery request, adds the delivery request passing the check to the message queue, and returns a receipt status notification (success or failure) to the billing system.
The core engine takes out a delivery request from the message queue for processing and calls a delivery module: the core engine inquires delivery channel information of the billing unit in a configuration database according to the ID of the billing unit; the core engine sends bill summary information, recipient information and delivery channel information to the delivery module.
The delivery module asynchronously carries out the delivery with the ticket and the delivery without the ticket:
the delivery module sends the encrypted parameters and the bill display link to a receiver through a delivery channel; the delivery person may download the plate file via the bill display link.
The core engine downloads the plate file of the bill and sends the plate file to the delivery module; the delivery module delivers the plate document to the recipient through a delivery channel.
Example four
Further, determining a plurality of steps as compensation nodes (see fig. 5, determining steps of ticket delivery, ticket-free delivery, ticket downloading and the like as compensation nodes);
setting a compensation table, wherein the compensation table comprises each compensation node ID and data (such as bill ID, delivery content and other information) related to each compensation node;
if a compensation node is abnormal, the core engine records the time of the abnormal occurrence in the compensation table, and executes the compensation node again at regular time (in this embodiment, the compensation node is executed again every 5 minutes, and is executed again at most 5 times); and when the compensation node is executed again, locking the data related to the compensation node according to the compensation table until the compensation node is executed.
The method has the advantages that a timing compensation mechanism is arranged, so that a receiver and an invoicing unit can know the step in which a certain ticket is clamped, and the user experience is further improved.
EXAMPLE five
Further, the data slices in the configuration database are stored on different servers. In the embodiment, the elastic search is utilized to realize the fast indexing of the sliced data.
The embodiment has the advantages that through data slicing, the retrieval speed is increased, and the downtime influence is reduced.
EXAMPLE six
An electronic bill multi-channel delivery system comprises a core engine, a configuration database and a delivery module, wherein delivery channel information configured by an invoicing unit is stored in the configuration database;
a service requester sends a delivery request to a core engine, wherein the delivery request comprises bill summary information, an ID of a billing unit and information of a receiver;
the core engine is in communication connection with the delivery module and is used for inquiring the delivery channel information of the billing unit in a configuration database according to the ID of the billing unit and sending the bill summary information, the receiver information and the delivery channel information to the delivery module;
the delivery module is asynchronously used for making the delivery with the ticket and the delivery without the ticket:
the delivery module carries out ticketless delivery: the delivery module converts the bill summary information and the receiver information into parameters required by a delivery channel and conducts RSA encryption on the parameters; the delivery module sends the encrypted parameters and the bill display link to a receiver through a delivery channel; (in this embodiment, the core engine obtains the bill showing link from the bill service platform and sends the showing link to the delivery module together with the bill summary information, the bill showing link, the receiver information and the delivery channel information.)
The delivery module judges whether the bill delivery is carried out, if the bill delivery is carried out, the core engine downloads the plate-type file of the bill and sends the plate-type file to the delivery module (in the embodiment, the core engine downloads the plate-type file of the bill from each local bill service platform); the delivery module sends the plate file to the recipient through a delivery channel.
The delivery channel is WeChat card package, Payment treasures invoice manager, short message, mail, Unionpay card package, etc. Different delivery channels require different parameters, such as payment treasures invoicing butler needing to pay treasures id to push to the user. The user can select whether to make the delivery with the ticket or without the ticket. In this embodiment, the delivery module determines whether to deliver the ticketed service according to the type of the delivery channel, for example, the short message, the treasury payment invoice manager, and the union pay card package are non-ticketed delivery channels; the mail is a ticketed delivery channel.
The beneficial effect of this embodiment lies in:
1. a plurality of delivery channels are provided to meet the requirement of diversity of the receiver;
2. the delivery process is divided into ticketless delivery and ticketed delivery, the ticketed delivery and the ticketless delivery are carried out asynchronously, and a receiver receives the ticketless delivery information in real time and then receives the plate-type file, so that the user experience is improved.
EXAMPLE seven
In this embodiment, the message queue and the core engine are respectively deployed in different servers, and the plurality of delivery modules are respectively deployed on different servers.
Referring to fig. 3 and 4, the core engine checks the received delivery request, and the specific steps for checking the delivery request are as follows:
performing idempotent verification on the delivery request ID by the core engine to screen out repeated delivery requests;
the core engine performs identity verification on a plurality of request parameters (such as bill types, bill conditions and the like) to verify the validity of the delivery request.
In this implementation, the billing entity is provided with a key, which the core engine also maintains. And the billing unit carries out ascending sequencing on the plurality of request parameters, carries out first encryption by using the key, and carries out second encryption by using the MD5 algorithm to obtain a first character string. The billing unit sends a delivery request containing the character string and a plurality of request parameters. The core engine inquires a key of the unit according to the ID of the billing unit, firstly encrypts a plurality of request parameters in the delivery request by using the key, and secondly encrypts by using an MD5 algorithm to obtain a second character string; and comparing the first character string with the second character string, and if the comparison result is consistent, passing the identity verification.
And the core engine adds the delivery request passing the verification into a message queue and sends a receiving state notice to a delivery request sender.
The core engine takes out the delivery request from the message queue for processing: the core engine processes the delivery request and judges whether the bill is repeated according to the bill ID, if so, the processing is stopped and the delivery request is abandoned. The core engine then polls for multiple delivery modules.
The method has the advantages that the delivery request is stored by using the message queue, and the core engine can immediately return the receiving state notification to the service requester after receiving the delivery request, so that the response efficiency of the delivery system is improved; under the condition of simultaneously receiving a large number of delivery requests, the delivery module concurrently processes a plurality of delivery requests, so that the delivery efficiency and the system stability are improved.
Example eight
In this embodiment, the billing service requester is a billing system;
as shown in fig. 2, the applicant performs payment and billing operations in the billing system. The billing system applies for ticket making to various local ticket service platforms and sends delivery requests to the delivery system.
A core engine in a delivery system receives a delivery request; the core engine checks the delivery request, adds the delivery request passing the check to the message queue, and returns a receipt status notification (success or failure) to the billing system.
The core engine takes out a delivery request from the message queue for processing and calls a delivery module: the core engine inquires delivery channel information of the billing unit in a configuration database according to the ID of the billing unit; the core engine sends bill summary information, recipient information and delivery channel information to the delivery module.
The delivery module asynchronously carries out the delivery with the ticket and the delivery without the ticket:
the delivery module sends the encrypted parameters and the bill display link to a receiver through a delivery channel; the delivery person may download the plate file via the bill display link.
The core engine downloads the plate file of the bill and sends the plate file to the delivery module; the delivery module delivers the plate document to the recipient through a delivery channel.
Example nine
Further, determining a plurality of steps as compensation nodes (see fig. 5, determining steps of ticket delivery, ticket-free delivery, ticket downloading and the like as compensation nodes);
setting a compensation table, wherein the compensation table comprises each compensation node ID and data (such as bill ID, delivery content and other information) related to each compensation node;
if a compensation node is abnormal, the core engine records the time of the abnormal occurrence in the compensation table, and executes the compensation node again at regular time (in this embodiment, the compensation node is executed again every 5 minutes, and is executed again at most 5 times); and when the compensation node is executed again, locking the data related to the compensation node according to the compensation table until the compensation node is executed.
The method has the advantages that a timing compensation mechanism is arranged, so that a receiver and an invoicing unit can know the step in which a certain ticket is clamped, and the user experience is further improved.
Example ten
Further, the data slices in the configuration database are stored on different servers. In the embodiment, the elastic search is utilized to realize the fast indexing of the sliced data.
The embodiment has the advantages that through data slicing, the retrieval speed is increased, and the downtime influence is reduced.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes performed by the present specification and drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. An electronic bill multi-channel delivery method is characterized by comprising the following steps:
s1, establishing a configuration database, wherein the configuration database stores delivery channel information configured by an invoicing unit;
s2, the service requester sends a delivery request to the core engine, wherein the delivery request comprises bill summary information, an ID of a billing unit and information of a receiver;
s3, the core engine processes the delivery request and calls a delivery module: the core engine inquires delivery channel information of the billing unit in a configuration database according to the ID of the billing unit; the core engine sends bill summary information, receiver information and delivery channel information to the delivery module;
s4, the delivery module asynchronously carries out the delivery with the ticket and the delivery without the ticket:
the delivery module carries out ticketless delivery: the delivery module converts the bill summary information and the receiver information into parameters required by a delivery channel and encrypts the parameters; the delivery module sends the encrypted parameters to a receiver through a delivery channel;
the delivery module judges whether the bill delivery is carried out or not, if the bill delivery is carried out, the core engine downloads the plate-type file of the bill and sends the plate-type file to the delivery module; the delivery module sends the plate file to the recipient through a delivery channel.
2. The multi-channel delivery method for electronic bills according to claim 1, wherein the delivery module is plural and is deployed on different servers respectively;
establishing a message queue;
the core engine checks the received delivery request, adds the delivery request passing the check into the message queue and sends a receiving state notification to a delivery request sender;
and the core engine takes the delivery request from the message queue for processing and polls and calls the plurality of delivery modules.
3. The electronic bill multi-channel delivery method as claimed in claim 2, wherein the delivery request further comprises a delivery request ID and a plurality of request parameters for describing the condition of the bill;
the specific steps for verifying the delivery request are as follows:
performing idempotent verification on the delivery request ID by the core engine to screen out repeated delivery requests;
the core engine performs identity verification on the request parameters to verify the validity of the delivery request.
4. The electronic bill multi-channel delivery method as claimed in claim 3, wherein the delivery request further includes a bill ID;
the core engine processes the delivery request and judges whether the bill is repeated according to the bill ID, if so, the processing is stopped and the delivery request is abandoned.
5. The electronic bill multi-channel delivery method according to claim 4, wherein the steps are determined as compensation nodes;
setting a compensation table, wherein the compensation table comprises each compensation node ID and data related to each compensation node;
if one compensation node is abnormal, the core engine records the abnormal time in the compensation table and executes the compensation node again at regular time; and when the compensation node is executed again, locking the data related to the compensation node according to the compensation table until the compensation node is executed.
6. The multi-channel delivery method of electronic bills according to claim 5, wherein the data segments in the configuration database are stored on different servers.
7. An electronic bill multi-channel delivery system is characterized by comprising a core engine, a configuration database and a delivery module, wherein delivery channel information configured by an invoicing unit is stored in the configuration database;
the service requester sends the delivery request to a core engine, wherein the delivery request comprises bill summary information, an ID of a billing unit and information of a receiver;
the core engine is in communication connection with the delivery module and is used for inquiring the delivery channel information of the billing unit in a configuration database according to the ID of the billing unit and sending the bill summary information, the receiver information and the delivery channel information to the delivery module;
the delivery module is used for asynchronously carrying out the delivery with the ticket and the delivery without the ticket:
the delivery module carries out ticketless delivery: the delivery module converts the bill summary information and the receiver information into parameters required by a delivery channel and encrypts the parameters; the delivery module sends the encrypted parameters to a receiver through a delivery channel;
the delivery module judges whether the bill delivery is carried out or not, if the bill delivery is carried out, the core engine downloads the plate-type file of the bill and sends the plate-type file to a delivery service; the delivery module delivers the plate document to the recipient through a delivery channel.
8. The electronic bill multi-channel delivery system according to claim 7, wherein the delivery module is plural and is deployed on different servers respectively;
establishing a message queue;
the core engine checks the received delivery request, adds the delivery request passing the check into the message queue and sends a receiving state notification to a delivery request sender;
and the core engine takes the delivery request from the message queue for processing and polls and calls the plurality of delivery modules.
9. The electronic bill multi-channel delivery system according to claim 8, wherein the delivery request further comprises a delivery request ID, a bill ID and a number of request parameters for describing the condition of the bill;
the delivery request is verified by the following steps: performing idempotent verification on the delivery request ID by the core engine to screen out repeated delivery requests; the core engine carries out identity verification on the plurality of request parameters so as to verify the validity of the delivery request;
and filtering the repeated bills according to the bill IDs, wherein the steps are as follows: the core engine processes the delivery request and judges whether the bill is repeated according to the bill ID, if so, the processing is stopped and the delivery request is abandoned.
10. The electronic bill multi-channel delivery system according to claim 9, wherein the steps are determined as compensation nodes;
setting a compensation table, wherein the compensation table comprises each compensation node ID and data related to each compensation node;
if one compensation node is abnormal, the core engine records the abnormal time in the compensation table and executes the compensation node again at regular time; and when the compensation node is executed again, locking the data related to the compensation node according to the compensation table until the compensation node is executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011564059.5A CN112561611B (en) | 2020-12-25 | 2020-12-25 | Electronic bill multi-channel delivery method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011564059.5A CN112561611B (en) | 2020-12-25 | 2020-12-25 | Electronic bill multi-channel delivery method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112561611A true CN112561611A (en) | 2021-03-26 |
| CN112561611B CN112561611B (en) | 2023-07-18 |
Family
ID=75032771
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011564059.5A Active CN112561611B (en) | 2020-12-25 | 2020-12-25 | Electronic bill multi-channel delivery method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112561611B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1744124A (en) * | 2005-09-16 | 2006-03-08 | 蔡军 | Network self-helf service system and its purchase-delivery method |
| FR2916070A1 (en) * | 2007-05-07 | 2008-11-14 | Digitick | Digital electronic ticket delivering method for e.g. sports event, involves generating electronic ticket image file from data using activation of connection unit, emitting file from sever towards terminal, and storing file to display file |
| CN109831414A (en) * | 2018-12-27 | 2019-05-31 | 大象慧云信息技术有限公司 | A kind of delivery management method and system of electronic invoice |
| CN112016715A (en) * | 2020-08-24 | 2020-12-01 | 航天信息股份有限公司 | Electronic invoice issuing and delivery system |
-
2020
- 2020-12-25 CN CN202011564059.5A patent/CN112561611B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1744124A (en) * | 2005-09-16 | 2006-03-08 | 蔡军 | Network self-helf service system and its purchase-delivery method |
| FR2916070A1 (en) * | 2007-05-07 | 2008-11-14 | Digitick | Digital electronic ticket delivering method for e.g. sports event, involves generating electronic ticket image file from data using activation of connection unit, emitting file from sever towards terminal, and storing file to display file |
| CN109831414A (en) * | 2018-12-27 | 2019-05-31 | 大象慧云信息技术有限公司 | A kind of delivery management method and system of electronic invoice |
| CN112016715A (en) * | 2020-08-24 | 2020-12-01 | 航天信息股份有限公司 | Electronic invoice issuing and delivery system |
Non-Patent Citations (2)
| Title |
|---|
| 叶保留: "《Android开发实验教程》", 30 September 2020 * |
| 袁燕妮: "《NoSQL数据库技术》", 31 August 2020 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112561611B (en) | 2023-07-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU758266B2 (en) | Remote image capture with centralized processing and storage | |
| US8494963B2 (en) | Remote image capture with centralized processing and storage | |
| US20140041006A1 (en) | Secure messaging center | |
| US20230230027A1 (en) | Method and apparatus for sign-bill return based on blockchain, device and readable storage medium | |
| US20140156785A1 (en) | Method and Apparatus for Generating User Notifications | |
| WO2003014999A1 (en) | System and method for providing secured electronic transactions | |
| CN113312649A (en) | Message processing method, device, equipment, system and storage medium | |
| TW201346636A (en) | Method for certifying delivery of data messages to mobile terminals | |
| CN112561611A (en) | Electronic bill multi-channel delivery method and system | |
| CN112256799A (en) | Data processing method and device based on block chain, server and storage medium | |
| CN110766485A (en) | Method for issuing electronic ticket based on short message | |
| CN104780519A (en) | Phone bill query method and system | |
| CN111311388A (en) | Invoice management system | |
| CN116071177A (en) | Method and device for distributing ticket to and from message based on message queue | |
| CN106651321A (en) | Unified electronic credential check method and system thereof | |
| CN113095835A (en) | Data consistency verification method, device and system | |
| CN115358682B (en) | Express delivery posting method, device and system and posting number book | |
| CN117495471A (en) | Method suitable for issuing digital-to-electricity invoice | |
| CN113627835A (en) | Distribution management method and device | |
| CN117952697A (en) | Method and system for full-electric ticket issuing cloud billing and certificate storage | |
| CN113642897A (en) | Order management method, device, equipment and storage medium | |
| CN116911722A (en) | Logistics quotation response method, device, equipment and medium thereof | |
| CN116029792A (en) | Multi-tenant payment access method and system based on mobile payment | |
| KR20240003068A (en) | Open-deal system and method | |
| CN111353831A (en) | Mobile billing method and device, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |