CN110689418A - Bill generation method and device - Google Patents
Bill generation method and device Download PDFInfo
- Publication number
- CN110689418A CN110689418A CN201910927944.6A CN201910927944A CN110689418A CN 110689418 A CN110689418 A CN 110689418A CN 201910927944 A CN201910927944 A CN 201910927944A CN 110689418 A CN110689418 A CN 110689418A
- Authority
- CN
- China
- Prior art keywords
- bill
- transaction data
- user
- link
- request information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 79
- 230000008569 process Effects 0.000 claims abstract description 46
- 238000012545 processing Methods 0.000 claims abstract description 37
- 230000000694 effects Effects 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 12
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000012546 transfer Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
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/125—Finance or payroll
-
- 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/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
One or more embodiments of the present specification disclose a method and an apparatus for generating a bill, which are used to integrate a bill generation process into one device, thereby achieving an effect of generating a bill quickly and easily. The method comprises the following steps: retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process; determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data; generating a bill for the first user based on the first transaction data.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a method and an apparatus for generating a bill.
Background
With the rapid increase of the number of merchants and the increasingly heavy tasks borne by the billing platform, one of the problems faced by the billing platform today is how to save resources as much as possible and ensure that a large number of merchant bills are produced in time.
The existing merchant billing system relies on the scheduling and quality detection functions provided by ODPS (Open Data Processing Service) to generate corresponding billing nodes, and the billing platform is only responsible for exporting bills in CSV (Comma-Separated Values) file format. The existing method disperses the life cycle of a single bill into two systems (namely a bill platform and an ODPS), so that the two systems need to be checked if the bill is in error, and the bill link is only more and more complicated as the number of bills is increased due to too flexible scheduling and too deep calling link of the ODPS.
Disclosure of Invention
One or more embodiments of the present disclosure provide a method and an apparatus for generating a bill, so as to integrate a bill generation process into a device, thereby achieving an effect of generating a bill quickly and easily.
To solve the above technical problem, one or more embodiments of the present specification are implemented as follows:
in one aspect, one or more embodiments of the present specification provide a bill generation method, including:
retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;
generating a bill for the first user based on the first transaction data.
In another aspect, one or more embodiments of the present specification provide a bill generation apparatus, including:
the calling module is used for calling related transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
the processing module is used for determining bill request information of the first user and processing the related transaction data according to the bill request information to obtain first transaction data;
and the generating module is used for generating a bill of the first user according to the first transaction data.
In yet another aspect, one or more embodiments of the present specification provide a bill generating apparatus, including:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;
generating a bill for the first user based on the first transaction data.
In yet another aspect, one or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following:
retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;
generating a bill for the first user based on the first transaction data.
By adopting the technical scheme of one embodiment of the specification, the generation process of the bill can be integrated on one device without depending on other platforms, so that the generation of the bill is faster and more unified; in addition, due to the unification of the bill generation links, the generation process of each bill is a clear linear link, so that various problems in the bill generation process are easy to check, and the error probability of the bill generation process can be reduced.
Drawings
In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in one or more embodiments of the present specification, and other drawings can be obtained by those skilled in the art without inventive exercise.
FIG. 1 is a schematic flow chart diagram of a method of generating a bill in accordance with one embodiment of the present description;
FIG. 2 is a schematic block diagram of a bill generation apparatus according to one embodiment of the present description;
fig. 3 is a schematic block diagram of a bill generating device according to an embodiment of the present specification.
Detailed Description
One or more embodiments of the present disclosure provide a method and an apparatus for generating a bill, so as to integrate a bill generation process into a device, thereby achieving an effect of generating a bill quickly and easily.
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.
Fig. 1 is a schematic flow chart of a bill generation method according to an embodiment of the present specification, and as shown in fig. 1, the bill generation method is applied to a bill platform and includes:
s102, relevant transaction data of the first user are called from at least one service node.
Each service node can be used as a domain for recording relevant transaction data generated in the transaction process of the user. The related transaction data may include any one or more of transaction data that may be generated during different types of transactions, such as transaction amount, transaction times, transaction time, transaction user information, and the like. Each service node may store transaction data for at least one transaction type, e.g., service node a for storing transaction data related to the transfer of money, service node b for storing transaction data related to the payment of money, service node c for storing transaction data related to the receipt of money, etc.
And S104, determining bill request information of the first user, and processing related transaction data according to the bill request information to obtain first transaction data.
The bill request information may include preset bill output rules, a request for generating one or more bills, a bill storage address, and other information. The processing manner of the related transaction data is different according to different information carried in the bill request information, and the specific processing manner will be described in detail in the following embodiments.
And S106, generating a bill of the first user according to the first transaction data.
By adopting the technical scheme of one embodiment of the specification, the generation process of the bill can be integrated on one device without depending on other platforms, so that the generation of the bill is faster and more unified; in addition, due to the unification of the bill generation links, the generation process of each bill is a clear linear link, so that various problems in the bill generation process are easy to check, and the error probability of the bill generation process can be reduced.
In one embodiment, before the above steps are performed, relevant transaction data generated during the user transaction process needs to be recorded on each service node. Since each service node is divided according to different transaction types, each service node is used for storing transaction data generated in different types of transaction processes, for example, related transaction data in a transfer process is recorded in the service node a, related transaction data in a payment process is recorded in the service node b, related transaction data in a collection process is recorded in the service node c, and the like.
In this embodiment, the related transaction data may be recorded according to the transaction information of the user during the transaction. For example, if the transaction information is "user a transfers 100 yuan to user B", the transaction data is analyzed to know that the payer is user a, the payee is user B, and the transaction amount is 100 yuan in the transaction process, and then the data of the payer, the payee, the transaction amount, and the like are recorded on the service node corresponding to the transfer transaction type.
After the relevant transaction data is recorded in each service node, the relevant transaction data of the user can be obtained from at least one service node when a bill needs to be generated for the user, and then the bill of the user is generated.
In one embodiment, after retrieving the relevant transaction data of the first user from the at least one service node, the relevant transaction data may be checked to determine whether the relevant transaction data is accurate, and after determining that the relevant transaction data is accurate, the billing request information of the first user is determined (i.e., execution S104).
In this embodiment, the related transaction data may be checked from multiple aspects, for example, whether the transaction amount recorded in the related transaction data is accurate, whether the transaction time is accurate, whether the user information related to the transaction is accurate, whether the recording format of the transaction data is accurate, and the like. When checking data such as transaction amount, transaction time, user information related to transaction and the like, the transaction information during user transaction can be firstly obtained, and the transaction information during user transaction can be stored in a designated storage area of a billing platform or other servers.
For example, the transaction information is "user a transfers 100 yuan to user B", and the relevant transaction data acquired from the service node is: the payer is user A, the payee is user B, and the transaction amount is 100 Yuan. And judging whether the acquired related transaction data is accurate or not by analyzing the transaction information and comparing the transaction information with the acquired related transaction data. If at least one item of related transaction data does not correspond to the transaction information, it can be determined that the acquired related transaction data is inaccurate.
In this embodiment, before generating the bill, by checking the correctness of each item of relevant transaction data recorded on the service node, it is ensured that the correct relevant transaction data is obtained, thereby ensuring that the accurate bill is generated for the user.
In one embodiment, the bill request information includes preset bill output rules. Therefore, when the related transaction data are processed according to the bill request information, the related transaction data can be summarized firstly to obtain a data wide table corresponding to the related transaction data; and then, correspondingly processing each related transaction data in the data wide table according to the bill output rule to obtain first transaction data according with the bill output rule.
The bill output rule is used for restricting the data output format of each item of relevant transaction data. For example, the bill output rule includes a timestamp format corresponding to the transaction time, the timestamp format being in the form of yyyyMMddHHmmss, where "yyyy" represents year, "MM" represents month, "dd" represents day, "HH" represents time, "MM" represents minute, and "ss" represents second.
In this embodiment, the acquired related transaction data is processed according to a preset bill output rule to obtain first transaction data, and then a bill of the user is generated according to the first transaction data, so that each item of transaction data in the generated bill of the user conforms to a certain rule, rather than a disordered form, and thus the user can check the transaction data conveniently, and the management of the transaction data by a bill platform is facilitated.
In one embodiment, bill generation links required to be executed for generating various bills respectively can be configured in advance, and respective node attributes are configured for each link node contained in each bill generation link; the node attribute comprises user information, operation types in the bill generation process and other information, and each bill generation link comprises at least one link node.
In this embodiment, each link node has configurability, which enables a configurator to configure each link node according to a business requirement, so that the configurator can simply, clearly and clearly manage each link node included in the bill generating link. In addition, the bill generation flow is nodulated, each operation step only needs to pay attention to the logic of the operation step without considering the environment, so that the operation logic of the operation step is simple and controllable for each individual link node, and the link nodes are mutually independent for the overall scheduling, so that the distributed scheduling is easily realized, and the system resources are utilized to the maximum extent.
Based on the above embodiment, if the bill request information includes a request for generating a plurality of bills, when the plurality of bills are generated, first, a bill generation link that needs to be executed for generating each bill needs to be determined; further determining the node attribute of each link node; then comparing the link nodes corresponding to the bill generating links to judge whether the node attributes of the link nodes corresponding to the bill generating links are the same or not; and if the link nodes with the same node attribute exist in the link nodes respectively corresponding to the bill generation links, merging the link nodes with the same node attribute in the bill generation links.
For example, the bill request information includes a request for generating a detailed bill and a summary bill of the transaction of the user a, that is, two bills need to be generated at the same time, and since the two bills are different, link nodes corresponding to bill generation links to be executed for generating each bill are different. Specifically, the bill generation link of the transaction statement bill includes a link node X, and the node attribute of the link node X is as follows: the user information is user A, and the operation type is transaction detail data acquisition. The bill generation link for summarizing the bill comprises a link node X and a link node Y, and the node attribute of the link node X is as follows: the user information is user A, the operation type is transaction detail data acquisition, and the node attribute of the link node Y is as follows: the user information is user A, and the operation type is summary all detail data. Therefore, the same link node X is included in the bill generation links of the transaction detail bill and the summary bill, so that the link node X corresponding to the transaction detail bill and the link node X corresponding to the summary bill can be merged.
In this embodiment, after the link nodes having the same node attribute are merged, the output results of the merged link nodes in different bills are also merged. Following the above example, after the link node X corresponding to the transaction statement bill and the link node X corresponding to the summary bill are merged (i.e., the operations for obtaining the statement data in the process of generating the two bills are merged), when the transaction statement bill and the summary bill are output, only one statement data needs to be output, and the statement data corresponding to the transaction statement bill and the statement data corresponding to the summary bill do not need to be output, so that resources are greatly saved.
In this embodiment, the link node X corresponding to the transaction statement bill and the link node X corresponding to the summary bill are merged, so that the operation corresponding to the link node having the same node attribute is executed only once, thereby avoiding the repeated execution of the same operation corresponding to the same link node by the bill platform, and greatly reducing the system load and resource consumption.
In one embodiment, the bill request information includes a bill storage address, and thus, after the bill of the first user is generated, the bill may be output to the bill storage address so that the first user can view the bill from the bill storage address.
In summary, particular embodiments of the present subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may be advantageous.
Based on the same idea, the bill generation method provided in one or more embodiments of the present specification further provides a bill generation device.
Fig. 2 is a schematic block diagram of a bill generation apparatus according to an embodiment of the present specification, and as shown in fig. 2, a bill generation apparatus 200 applied to a bill platform includes:
a retrieval module 210 for retrieving the relevant transaction data of the first user from at least one service node; the service node is used for recording relevant transaction data generated in the user transaction process;
the processing module 220 determines bill request information of the first user, and processes the related transaction data according to the bill request information to obtain first transaction data;
the generating module 230 generates a bill of the first user according to the first transaction data.
In one embodiment, the bill request information includes preset bill output rules;
the processing module 220 includes:
the summarizing unit summarizes the related transaction data to obtain a data width table corresponding to the related transaction data;
and the processing unit is used for correspondingly processing each related transaction data in the data wide table according to the bill output rule to obtain first transaction data conforming to the bill output rule.
In one embodiment, the apparatus 200 further comprises:
the checking module is used for checking the related transaction data after the related transaction data of the first user is called from at least one service node so as to judge whether the related transaction data is accurate or not;
the processing module 220 includes:
and the determining unit is used for determining the bill request information of the first user after determining that the related transaction data is accurate.
In one embodiment, the billing request information includes a request to generate a plurality of bills;
the apparatus 200 further comprises:
the first determining module is used for determining a bill generating link which needs to be executed for generating each bill; each bill generation link comprises at least one link node;
the second determining module is used for determining the node attribute of each link node; the node attribute comprises at least one item of information in user information and operation types in a bill generation process;
the comparison module is used for comparing the link nodes corresponding to the bill generation links to judge whether the node attributes of the link nodes corresponding to the bill generation links are the same or not;
and the merging module is used for merging the link nodes respectively corresponding to the bill generation links if the node attributes of the link nodes respectively corresponding to the bill generation links are the same.
In one embodiment, the apparatus 200 further comprises:
the configuration module is used for configuring bill generation links required to be executed for generating various bills respectively before determining the bill generation links required to be executed for generating the bills respectively; and configuring respective node attributes for each link node included in the bill generation link.
In one embodiment, the billing request information further includes a billing storage address;
the apparatus 200 further comprises:
and the output module outputs the bill to the bill storage address.
By adopting the device of one embodiment of the specification, the generation process of the bill can be integrated on one device without depending on other platforms, so that the generation of the bill is faster and more unified; in addition, due to the unification of the bill generation links, the generation process of each bill is a clear linear link, so that various problems in the bill generation process are easy to check, and the error probability of the bill generation process can be reduced.
It should be understood by those skilled in the art that the above bill generation apparatus can be used to implement the above bill generation method, and the detailed description thereof should be similar to the above method, and therefore, in order to avoid complexity, no further description is provided herein.
Based on the same idea, one or more embodiments of the present specification further provide a bill generating apparatus, as shown in fig. 3. The bill generating devices may vary significantly depending on configuration or performance and may include one or more processors 301 and memory 302, where the memory 302 may have one or more stored applications or data stored therein. Memory 302 may be, among other things, transient storage or persistent storage. The application program stored in memory 302 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a statement generation device. Still further, processor 301 may be configured to communicate with memory 302 to execute a series of computer-executable instructions in memory 302 on a bill generating device. The bill generation apparatus may also include one or more power supplies 303, one or more wired or wireless network interfaces 304, one or more input-output interfaces 305, one or more keyboards 306.
In particular, in this embodiment, the bill generating apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions in the bill generating apparatus, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:
retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;
generating a bill for the first user based on the first transaction data.
Optionally, the bill request information includes preset bill output rules;
the computer executable instructions, when executed, may further cause the processor to:
summarizing the related transaction data to obtain a data width table corresponding to the related transaction data;
and correspondingly processing each related transaction data in the data wide table according to the bill output rule to obtain the first transaction data according with the bill output rule.
Optionally, the computer executable instructions, when executed, may further cause the processor to:
after the relevant transaction data of the first user is called from at least one service node, checking the relevant transaction data to judge whether the relevant transaction data is accurate or not;
and when the related transaction data is determined to be accurate, determining the bill request information of the first user.
Optionally, the billing request information includes a request to generate a plurality of bills;
the computer executable instructions, when executed, may further cause the processor to:
determining a bill generation link which needs to be executed for generating each bill; each bill generation link comprises at least one link node;
determining a node attribute of each link node; the node attribute comprises at least one item of information of user information and operation types in a bill generation process;
comparing the link nodes corresponding to the bill generation links to judge whether the node attributes of the link nodes corresponding to the bill generation links are the same or not;
and if so, merging the link nodes respectively corresponding to the bill generation links.
Optionally, the computer executable instructions, when executed, may further cause the processor to:
configuring a bill generation link which needs to be executed for generating each bill respectively before determining a bill generation link which needs to be executed for generating each bill respectively; and configuring respective node attributes for each link node included in the bill generation link.
Optionally, the bill request information further includes a bill storage address;
the computer executable instructions, when executed, may further cause the processor to:
and outputting the bill to the bill storage address.
One or more embodiments of the present specification also propose a computer-readable storage medium storing one or more programs, the one or more programs including instructions, which when executed by an electronic device including a plurality of application programs, enable the electronic device to perform the above bill generation method, and in particular to perform:
retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;
generating a bill for the first user based on the first transaction data.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the various elements may be implemented in the same one or more software and/or hardware implementations in implementing one or more embodiments of the present description.
One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
One or more embodiments of the present specification are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only one or more embodiments of the present disclosure, and is not intended to limit the present disclosure. Various modifications and alterations to one or more embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of the present specification should be included in the scope of claims of one or more embodiments of the present specification.
Claims (12)
1. A bill generation method comprising:
retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;
generating a bill for the first user based on the first transaction data.
2. The method of claim 1, the bill request information including preset bill output rules;
the processing the related transaction data according to the bill request information to obtain first transaction data includes:
summarizing the related transaction data to obtain a data width table corresponding to the related transaction data;
and correspondingly processing each related transaction data in the data wide table according to the bill output rule to obtain the first transaction data according with the bill output rule.
3. The method of claim 1, after retrieving the relevant transaction data for the first user from the at least one service node, further comprising:
checking the related transaction data to judge whether the related transaction data is accurate or not;
the determining the billing request information of the first user comprises:
and when the related transaction data is determined to be accurate, determining the bill request information of the first user.
4. The method of claim 1, the billing request information comprising a request to generate a plurality of bills;
the method further comprises the following steps:
determining a bill generation link which needs to be executed for generating each bill; each bill generation link comprises at least one link node;
determining a node attribute of each link node; the node attribute comprises at least one item of information of user information and operation types in a bill generation process;
comparing the link nodes corresponding to the bill generation links to judge whether the node attributes of the link nodes corresponding to the bill generation links are the same or not;
and if so, merging the link nodes respectively corresponding to the bill generation links.
5. The method of claim 4, wherein prior to determining a bill generation link to be performed for each of the bills, the method further comprises:
configuring a bill generation link which is required to be executed for generating various bills respectively; and configuring respective node attributes for each link node included in the bill generation link.
6. The method of claim 1, the billing request information further comprising a billing storage address;
the method further comprises the following steps:
and outputting the bill to the bill storage address.
7. A bill generation apparatus comprising:
the calling module is used for calling related transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
the processing module is used for determining bill request information of the first user and processing the related transaction data according to the bill request information to obtain first transaction data;
and the generating module is used for generating a bill of the first user according to the first transaction data.
8. The apparatus of claim 7, the bill request information comprising preset bill output rules;
the processing module comprises:
the summarizing unit summarizes the related transaction data to obtain a data width table corresponding to the related transaction data;
and the processing unit is used for correspondingly processing each related transaction data in the data wide table according to the bill output rule to obtain the first transaction data which accords with the bill output rule.
9. The apparatus of claim 7, further comprising:
the checking module is used for checking the related transaction data of the first user after the related transaction data of the first user is called from at least one service node so as to judge whether the related transaction data is accurate or not;
the processing module comprises:
and the first determining unit is used for determining the bill request information of the first user after the related transaction data is determined to be accurate.
10. The apparatus of claim 7, the billing request information comprising a request to generate a plurality of bills;
the device further comprises:
the first determining module is used for determining a bill generating link which needs to be executed for generating each bill; each bill generation link comprises at least one link node;
the second determining module is used for determining the node attribute of each link node; the node attribute comprises at least one item of information of user information and operation types in a bill generation process;
the comparison module is used for comparing the link nodes corresponding to the bill generation links to judge whether the node attributes of the link nodes corresponding to the bill generation links are the same or not;
and the merging module is used for merging the link nodes respectively corresponding to the bill generation links if the node attributes of the link nodes respectively corresponding to the bill generation links are the same.
11. A bill generation device comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;
generating a bill for the first user based on the first transaction data.
12. A storage medium storing computer-executable instructions that, when executed, implement the following:
retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process;
determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;
generating a bill for the first user based on the first transaction data.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310237443.1A CN116993519A (en) | 2019-09-27 | 2019-09-27 | Bill generation method and device |
| CN201910927944.6A CN110689418B (en) | 2019-09-27 | 2019-09-27 | Bill generation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910927944.6A CN110689418B (en) | 2019-09-27 | 2019-09-27 | Bill generation method and device |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310237443.1A Division CN116993519A (en) | 2019-09-27 | 2019-09-27 | Bill generation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110689418A true CN110689418A (en) | 2020-01-14 |
| CN110689418B CN110689418B (en) | 2023-04-07 |
Family
ID=69110772
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910927944.6A Active CN110689418B (en) | 2019-09-27 | 2019-09-27 | Bill generation method and device |
| CN202310237443.1A Pending CN116993519A (en) | 2019-09-27 | 2019-09-27 | Bill generation method and device |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310237443.1A Pending CN116993519A (en) | 2019-09-27 | 2019-09-27 | Bill generation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN110689418B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111402030A (en) * | 2020-03-06 | 2020-07-10 | 中国建设银行股份有限公司 | Bill generation method and device |
| CN112182505A (en) * | 2020-09-09 | 2021-01-05 | 支付宝(杭州)信息技术有限公司 | Account compliance processing method and device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011026350A1 (en) * | 2009-09-03 | 2011-03-10 | 中兴通讯股份有限公司 | Route selection apparatus and route selection method for multi-service recovery |
| CN102158531A (en) * | 2010-02-01 | 2011-08-17 | 北京大学 | Distributed transmission method for query data stream |
| CN104932982A (en) * | 2014-03-21 | 2015-09-23 | 华为技术有限公司 | Message access memory compiling method and related apparatus |
| CN106156265A (en) * | 2015-06-08 | 2016-11-23 | 北京天禾元创软件股份有限公司 | For the method and apparatus merging tree structure |
| CN108985736A (en) * | 2017-06-02 | 2018-12-11 | 深圳市银信网银科技有限公司 | Processing method, device and the terminal of bill |
| CN109684408A (en) * | 2018-12-07 | 2019-04-26 | 深圳市智税链科技有限公司 | Data managing method, device, medium and the electronic equipment of block catenary system |
| CN110070350A (en) * | 2019-03-25 | 2019-07-30 | 中金支付有限公司 | A kind of payment transaction settlement processing method and system |
| CN110147992A (en) * | 2019-04-29 | 2019-08-20 | 阿里巴巴集团控股有限公司 | Bill generation method and device and electronic equipment based on block chain |
-
2019
- 2019-09-27 CN CN201910927944.6A patent/CN110689418B/en active Active
- 2019-09-27 CN CN202310237443.1A patent/CN116993519A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011026350A1 (en) * | 2009-09-03 | 2011-03-10 | 中兴通讯股份有限公司 | Route selection apparatus and route selection method for multi-service recovery |
| CN102158531A (en) * | 2010-02-01 | 2011-08-17 | 北京大学 | Distributed transmission method for query data stream |
| CN104932982A (en) * | 2014-03-21 | 2015-09-23 | 华为技术有限公司 | Message access memory compiling method and related apparatus |
| CN106156265A (en) * | 2015-06-08 | 2016-11-23 | 北京天禾元创软件股份有限公司 | For the method and apparatus merging tree structure |
| CN108985736A (en) * | 2017-06-02 | 2018-12-11 | 深圳市银信网银科技有限公司 | Processing method, device and the terminal of bill |
| CN109684408A (en) * | 2018-12-07 | 2019-04-26 | 深圳市智税链科技有限公司 | Data managing method, device, medium and the electronic equipment of block catenary system |
| CN110070350A (en) * | 2019-03-25 | 2019-07-30 | 中金支付有限公司 | A kind of payment transaction settlement processing method and system |
| CN110147992A (en) * | 2019-04-29 | 2019-08-20 | 阿里巴巴集团控股有限公司 | Bill generation method and device and electronic equipment based on block chain |
Non-Patent Citations (2)
| Title |
|---|
| LI RUNZHOU等: ""Structured Bill of Material Design and Consistency Maintenance in Drilling Industry"", 《2014 FIFTH INTERNATIONAL CONFERENCE ON INTELLIGENT SYSTEMS DESIGN AND ENGINEERING APPLICATIONS》 * |
| 刘跃军等: "XML数据库的索引技术研究", 《微计算机信息 》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111402030A (en) * | 2020-03-06 | 2020-07-10 | 中国建设银行股份有限公司 | Bill generation method and device |
| CN112182505A (en) * | 2020-09-09 | 2021-01-05 | 支付宝(杭州)信息技术有限公司 | Account compliance processing method and device |
| CN112182505B (en) * | 2020-09-09 | 2024-05-31 | 支付宝(杭州)信息技术有限公司 | Accounting compliance processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116993519A (en) | 2023-11-03 |
| CN110689418B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107424069B (en) | Wind control feature generation method, risk monitoring method and equipment | |
| CN110648138B (en) | Transaction query and transaction data processing method, device and equipment based on block chain | |
| CN111967849A (en) | Task processing flow arrangement method and device and electronic equipment | |
| CN108173706B (en) | Service marking method, device and equipment under multi-service system | |
| CN110472438B (en) | Transaction data processing and transaction inquiring method, device and equipment based on blockchain | |
| CN108985742B (en) | Transaction processing method and device and block chain system | |
| CN107705199B (en) | Generation method and device of feature calculation code | |
| CN106557486A (en) | A kind of storage method and device of data | |
| CN107391532B (en) | Data filtering method and device | |
| CN111539811B (en) | Risk account identification method and device | |
| CN107066519A (en) | A kind of task detection method and device | |
| CN108830705B (en) | Method, device and equipment for summarizing transaction data | |
| CN110689418B (en) | Bill generation method and device | |
| CN108599973A (en) | A kind of daily record correlating method, device and equipment | |
| CN110389989B (en) | Data processing method, device and equipment | |
| CN109359109B (en) | Data processing method and system based on distributed stream computing | |
| CN107633015A (en) | A kind of data processing method, device and equipment | |
| CN110175201A (en) | Business data processing method, system, device and electronic equipment | |
| TW202032466A (en) | User age prediction method, apparatus, and device | |
| CN111046052B (en) | Method, device and equipment for storing operation records in database | |
| CN110489418B (en) | Data aggregation method and system | |
| CN109615379B (en) | Generating method and device of rejection processing system | |
| CN110008386B (en) | Data generation, processing and evaluation method, device, equipment and medium | |
| CN109039695B (en) | Service fault processing method, device and equipment | |
| CN115423461A (en) | Bill processing method and device |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240219 Address after: Room 1408, No. 447 Nanquan North Road, China (Shanghai) Pilot Free Trade Zone, Pudong New Area, Shanghai, 200120 Patentee after: Shanghai Ant Chuangjiang Information Technology Co.,Ltd. Country or region after: China Address before: 310000 801-11 section B, 8th floor, 556 Xixi Road, Xihu District, Hangzhou City, Zhejiang Province Patentee before: Alipay (Hangzhou) Information Technology Co.,Ltd. Country or region before: China |
|
| TR01 | Transfer of patent right |