A highway pass data reconciliation method and related device

Abstract

The application discloses a highway passing data difference rolling method and related equipment, and the highway passing data difference rolling method obtains a settlement income table corresponding to a current settlement period from a database; a daily settlement report is generated according to a corresponding relationship between the settlement income table corresponding to the current settlement period and an overall income report; and the daily settlement report dynamically changes with payment and account transfer. According to the embodiment of the application, the electronic equipment can obtain the settlement income table corresponding to the current settlement period from the database, and generate the daily settlement report according to the corresponding relationship between the overall income report integrated from previous historical income and the settlement income table, and the daily settlement report dynamically changes with the payment and account transfer, so that the efficiency of checking the settlement data generated by the vehicle passing of the highway can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer technology, and belongs to the technical field of Internet of Things, and specifically relates to a highway passing data difference rolling method and related equipment. BACKGROUND

[0002] The highway toll system is a system for collecting vehicle tolls, which usually includes toll stations, billing devices, and management back-end components. The highway toll system can identify vehicles by recognizing license plate numbers or using electronic tags, and can implement online payment and invoice printing functions. At the same time, the highway toll system can also realize traffic flow monitoring and road condition prediction functions through data analysis and intelligent prediction technology, providing strong support for the management and operation of highways.

[0003] However, a large number of vehicles pass through the highway every day, resulting in a large amount of checkout data, and the query efficiency of these data still needs to be improved. SUMMARY

[0004] In view of at least one of the above technical problems, the purpose of the present application is to provide a highway passing data difference rolling method and related equipment.

[0005] In one aspect, the present application embodiment includes a highway passing data difference rolling method applied to an electronic device, comprising:

[0006] Obtain the owner settlement income table corresponding to the current settlement period from the database;

[0007] According to the correspondence between the settlement income table corresponding to the current settlement period and the overall income report, generate a daily settlement report; the daily settlement report dynamically changes with payment and account transfer.

[0008] Further, the owner settlement income table includes a plurality of owner data; after obtaining the owner settlement income table corresponding to the current settlement period from the database, the method further comprises:

[0009] Summarize and generate an owner income record table for the owner data in the owner settlement income table that meets the preset actual payment condition;

[0010] According to the owner income record table, generate a corresponding owner account transfer instruction table and owner account transfer instruction history table.

[0011] Further, the generating of the corresponding owner account transfer instruction table and owner account transfer instruction history table according to the owner income record table comprises:

[0012] Based on the owner revenue record table and the overall revenue report, netting and settlement processing is performed to generate an owner netting data record table.

[0013] The owner remittance instruction table is generated based on the data in the owner netting data record table that meets the preset remittance conditions;

[0014] Multiple payment results are obtained from the owner payment instruction table, and the owner payment instruction history table is generated based on the multiple payment results.

[0015] Furthermore, before generating the daily settlement report based on the correspondence between the settlement revenue statement and the overall revenue statement corresponding to the current settlement period, the method further includes:

[0016] Obtain owner settlement information;

[0017] Based on the owner settlement information, the overall revenue report can be obtained.

[0018] Further, the step of generating a daily settlement report based on the correspondence between the settlement revenue statement and the overall revenue statement corresponding to the current settlement period includes:

[0019] Based on the settlement revenue table, the owner's payment instruction table and the owner's payment instruction history table are associated, and queries are performed in the owner's payment instruction table and the owner's payment instruction history table to obtain the first payment dimension;

[0020] The second payment dimension is obtained by associating the owner payment instruction table and the owner payment instruction history table with the overall revenue report, and querying the owner payment instruction table and the owner payment instruction history table.

[0021] The daily settlement report is obtained based on the data corresponding to the first and second payment dimensions, respectively.

[0022] Further, the step of associating the settlement revenue table with the owner's payment instruction table and the owner's payment instruction history table, and querying the owner's payment instruction table and the owner's payment instruction history table to obtain the first payment dimension includes:

[0023] Based on the owner code and daily settlement serial number in the settlement income table, link it to the owner income record table;

[0024] Based on the netting batch number and owner code in the owner revenue record table, the left link is established to the owner netting data record table;

[0025] Based on the road segment code and instruction number in the owner netting data record table, the data is left-linked to the owner reimbursement instruction table and the owner reimbursement instruction history table, and a query is performed in the owner reimbursement instruction table and the owner reimbursement instruction history table to obtain the first reimbursement dimension.

[0026] Furthermore, the step of associating the owner's payment instruction table and the owner's payment instruction history table with the overall revenue report, and querying the owner's payment instruction table and the owner's payment instruction history table to obtain the second payment dimension includes:

[0027] Based on the netting batch number, owner code, settlement month, settlement date, and start date of payment transfer in the overall revenue report, the data is linked to the owner netting data record table.

[0028] Based on the road segment code and instruction number in the owner netting data record table, the system is left-linked to the owner remittance instruction table and the owner remittance instruction history table, and queries are performed in the owner remittance instruction table and the owner remittance instruction history table to obtain the second remittance dimension.

[0029] On the other hand, embodiments of the present invention include a highway traffic data recalculation device, applied to electronic equipment, the device comprising:

[0030] The settlement acquisition module is used to retrieve the owner settlement revenue table corresponding to the current settlement period from the database;

[0031] The report correspondence module is used to generate a daily settlement report based on the correspondence between the settlement revenue report and the overall revenue report corresponding to the current settlement period; the daily settlement report changes dynamically with payment and transfer.

[0032] On the other hand, this application discloses an electronic device, including a memory and a processor. The memory stores a computer program, and when the computer program is executed by the processor, the processor enables the processor to implement any of the highway traffic data netting methods disclosed in this application.

[0033] On the other hand, embodiments of the present invention also include a storage medium storing a processor-executable program, which, when executed by a processor, is used to perform the highway traffic data netting method in the embodiments.

[0034] Compared with related technologies, the embodiments of this application have the following beneficial effects:

[0035] This application provides a method and related equipment for netting highway traffic data. The method retrieves the settlement revenue table corresponding to the current settlement period from a database; generates a daily settlement report based on the correspondence between the settlement revenue table for the current settlement period and the overall revenue report; and the daily settlement report dynamically changes with payment processing. By implementing this application, the electronic device can retrieve the settlement revenue table corresponding to the current settlement period from the database, and generate a daily settlement report based on the overall revenue report compiled from historical revenue and the correspondence between the settlement revenue tables. This daily settlement report dynamically changes with payment processing, improving the efficiency of viewing settlement data generated by highway vehicle traffic. Attached Figure Description

[0036] Figure 1 This is an application scenario diagram of a highway traffic data netting method disclosed in an embodiment of this application;

[0037] Figure 2 This is a flowchart illustrating a method for offsetting highway traffic data disclosed in an embodiment of this application;

[0038] Figure 3 This is a schematic diagram showing a daily settlement report in one embodiment of this application;

[0039] Figure 4 This is a flowchart illustrating the process of generating a daily settlement report based on the correspondence between the settlement income table corresponding to the current settlement period and the overall income report, as disclosed in the embodiments of this application.

[0040] Figure 5 This is a schematic diagram of the structure of a highway traffic data differential device disclosed in an embodiment of this application;

[0041] Figure 6 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of this application. Detailed Implementation

[0042] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] It should be noted that the terms "comprising" and "having," and any variations thereof, in the embodiments and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0044] It is understood that the terms "first," "second," etc., used in this application may be used to describe various elements herein, but these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of this application, a first remittance dimension may be referred to as a second remittance dimension, and similarly, a second remittance dimension may be referred to as a first remittance dimension. Both the first remittance dimension and the second remittance dimension are remittance dimensions, but they are not the same remittance dimension.

[0045] This application discloses a method and related equipment for netting highway traffic data, which can improve the efficiency of viewing settlement data generated by vehicle traffic on highways. These will be described in detail below.

[0046] Please see Figure 1 , Figure 1 This is an application scenario diagram of a highway traffic data netting method disclosed in an embodiment of this application. The highway traffic data netting method is applicable to electronic devices, including but not limited to mobile phones, tablets, wearable devices, laptops, and PCs (Personal Computers), etc., which are not limited in this embodiment. Electronic device 101 retrieves the settlement revenue table corresponding to the current settlement period from the database, and generates a daily settlement report based on the correspondence between the settlement revenue table corresponding to the current settlement period and the overall revenue report; the daily settlement report changes dynamically with payment transfers.

[0047] Figure 2 This is a flowchart illustrating a highway traffic data netting method disclosed in an embodiment of this application. Figure 2 The described highway traffic data netting method is applicable to the aforementioned electronic equipment. For example... Figure 2 As shown, the highway traffic data netting method may include the following steps:

[0048] Step S201: Retrieve the settlement revenue table corresponding to the current settlement period from the database.

[0049] Step S202: Generate a daily settlement report based on the correspondence between the settlement revenue statement and the overall revenue statement for the current settlement period; the daily settlement report changes dynamically with payment and transfer.

[0050] In some embodiments, the owner settlement income statement contains data on multiple owners. After retrieving the owner settlement income statement corresponding to the current settlement period from the database, the electronic device can aggregate the owner data in the owner settlement income statement that meets the preset actual payment conditions and generate an owner income record table. Based on the owner income record table, it generates a corresponding owner transfer instruction table and an owner transfer instruction history table. The owner data can be the data in the owner settlement income statement used to record owner settlement records.

[0051] Furthermore, the electronic device can perform netting and settlement processing based on the owner's revenue record table and the overall revenue report, generating an owner netting data record table; based on the data in the owner netting data record table that meets preset transfer conditions, it generates an owner transfer instruction table; based on the owner transfer instruction table, it obtains multiple transfer results and generates an owner transfer instruction history table based on these multiple transfer results. In other words, when owners make daily settlements, the electronic device can obtain the owner settlement revenue table data that meets the daily settlement requirements and generate an owner revenue record table. Based on the data in the owner revenue record table, it summarizes the owners' calculations to obtain an owner revenue record table and a transaction reconciliation data summary table, and performs netting and settlement processing on these tables to generate an owner netting data record table. It then generates an owner transfer instruction table from the owner data in the owner netting data record table that meets the transfer conditions. Based on the owner data in the owner transfer instruction table, it sends the transfer to the bank. The bank returns the transfer result, and after a successful transfer, the owner data in the owner transfer instruction table is moved to the owner transfer instruction history table.

[0052] As an optional implementation, the electronic device can acquire owner settlement information and, based on this information, retrieve an overall revenue report. The owner settlement information may include the owner's code and settlement date. Based on this information, the corresponding overall revenue report is retrieved from the database. After retrieving the overall revenue report, the electronic device can generate a daily settlement report based on the correspondence between the settlement revenue report for the current settlement period and the overall revenue report.

[0053] In some embodiments, the settlement date can be used to describe the settlement date corresponding to the daily three-in-one settlement; the settlement amount can be used to describe the settlement amount that has been settled daily; the instruction sending date can be used to describe the date the instruction is sent daily; and the pre-netting revenue can be used to describe the settlement amount for the instruction sent. The daily settlement report can be based on the three-in-one settlement data and summarize the owner's revenue transfer status according to the settlement date of the road segment owner. The electronic device only displays the instruction date and netting revenue after sending the owner's transfer instruction, and the data in the daily settlement report will change dynamically as payment is transferred. After the owner's transfer instruction is sent, the instruction sending date and pre-netting revenue columns are displayed, and the pre-netting revenue equals the settlement amount.

[0054] like Figure 3 As shown, Figure 3 This is a schematic diagram of a daily settlement report in one embodiment of this application. The daily settlement report can display the road segment name, settlement date, fund type, settlement amount, instruction sending date, and the accounting dimension of the pre-netting revenue.

[0055] In this embodiment, the electronic device retrieves the settlement revenue table corresponding to the current settlement period from the database; based on the correspondence between the settlement revenue table corresponding to the current settlement period and the overall revenue report, it generates a daily settlement report; the daily settlement report dynamically changes with payment transfers. By implementing this embodiment, the electronic device can retrieve the settlement revenue table corresponding to the current settlement period from the database, and generate a daily settlement report based on the overall revenue report integrated from past revenues and the correspondence between the settlement revenue tables. Furthermore, this daily settlement report dynamically changes with payment transfers, improving the efficiency of viewing settlement data generated by vehicle passage on highways.

[0056] Figure 4 This is a flowchart illustrating the process of generating a daily settlement report based on the correspondence between the settlement revenue table corresponding to the current settlement period and the overall revenue report, as disclosed in an embodiment of this application. Figure 4 As shown, the steps generate a daily settlement report based on the correspondence between the settlement income statement and the overall income statement for the current settlement period. This may also include the following steps:

[0057] Step S401: Based on the settlement revenue table, associate the owner's payment instruction table and the owner's payment instruction history table, and query the owner's payment instruction table and the owner's payment instruction history table to obtain the first payment dimension.

[0058] Step S402: Based on the overall revenue report, associate the owner's payment instruction table and the owner's payment instruction history table, and query the owner's payment instruction table and the owner's payment instruction history table to obtain the second payment dimension.

[0059] Step S403: Obtain the daily settlement report based on the data corresponding to the first and second payment dimensions respectively.

[0060] In some embodiments, the Owner Settlement Revenue Table, Owner Revenue Record Table, Owner Netting Data Record Table, Owner Transfer Instruction Table, and Owner Transfer Instruction History Table can all be reports in this database. The first transfer dimension may include fields such as Owner Code, Settlement Date, Funding System, Card Type, Inter-provincial Identifier, Revenue Amount (cents), Daily Settlement Transaction Number, Netting Batch Number, Instruction Number, Road Segment Code, and Instruction Generation Date. The second transfer dimension may include fields such as Owner Code, Revenue Road Segment Code, Actual Amount Received, Netting Batch Number, Settlement Month, Settlement Date, Transfer Initiation Date, Instruction Number, and Instruction Generation Date.

[0061] As an optional implementation, the electronic device can left-link to the owner revenue record table based on the owner code and daily settlement serial number in the settlement revenue table; left-link to the owner netting data record table based on the netting batch number and owner code in the owner revenue record table; and left-link to the owner payment instruction table and the owner payment instruction history table based on the road segment code and instruction number in the owner netting data record table, and query the owner payment instruction table and the owner payment instruction history table to obtain the first payment dimension.

[0062] In other words, electronic devices can query the owner settlement income table through the owner code and settlement date, thereby obtaining daily settlement data and information such as owner code, settlement date, fund system, card type, cross-province identification, income amount (cents), and daily settlement serial number in the owner settlement income table.

[0063] The owner code and daily settlement serial number are obtained from the owner settlement revenue table and then linked to the owner revenue record table to obtain the fields: owner code, settlement date, funding system, card type, inter-provincial identifier, revenue amount (cents), daily settlement serial number, and netting batch number. The netting batch number and owner code are obtained from the owner revenue record table and then linked to the owner netting data record table to obtain the fields: owner code, settlement date, funding system, card type, inter-provincial identifier, revenue amount (cents), daily settlement serial number, netting batch number, instruction number, and road segment code. The road segment code and instruction number obtained from the owner netting data record table are then linked to the owner payment instruction table and the owner payment instruction history table to obtain the first payment dimension.

[0064] As an optional implementation method, the electronic device left-links to the owner netting data record table based on the netting batch number, owner code, settlement month, settlement date, and start date of payment in the overall revenue report; and left-links to the owner payment instruction table and the owner payment instruction history table based on the road segment code and instruction number in the owner netting data record table, and queries the owner payment instruction table and the owner payment instruction history table to obtain the second payment dimension.

[0065] In other words, the electronic device can query the overall revenue report based on the owner code and settlement date, and obtain the owner code, revenue segment code, actual amount received, netting batch number, settlement month, settlement date, and start date of payment transfer. Within the overall revenue report, the netting batch number, owner code, settlement month, settlement date, and start date of payment transfer are retrieved, and then left-linked to the owner netting data record table to obtain the fields for owner code, revenue segment code, actual amount received, netting batch number, settlement month, settlement date, start date of payment transfer, and instruction number. The revenue segment code and instruction number fields are obtained from the owner netting data record table, and left-linked to the owner payment transfer instruction table and the owner payment transfer instruction history table based on the revenue segment code and instruction number. The second payment dimension is then queried from the owner payment transfer instruction table and the owner payment transfer instruction history table.

[0066] Furthermore, electronic devices can be converted into fields in the daily settlement report based on the fields included in the first payment dimension and the first field conversion relationship. Similarly, electronic devices can also be converted into fields in the daily settlement report based on the fields included in the second payment dimension and the second field conversion relationship. The conversion relationships for the first field conversion relationship are shown in Table 1.

[0067] Table 1

[0068] Fields in the first transfer dimension Fields in the daily settlement report Route segment code Route segment name Settlement date Settlement date Income amount Settlement amount Instruction generation date Instruction sending date Income amount Income before the difference Fund system, card type, cross-province identification Fund type

[0069] The transformation relationships for the second field are shown in Table 2:

[0070] Table 2

[0071] Fields in the second transfer dimension Fields in the daily settlement report Income route segment code Route segment name Settlement date Settlement date Collected amount Settlement amount Instruction generation date Instruction sending date Collected amount Income before the difference Cross-province transaction account income Fund type

[0072] The electronic device undergoes multiple levels of correlation and transformation, and the transformed data is finally formed into a complete record, which is displayed in the form of a report, thus obtaining a daily settlement report.

[0073] In this embodiment, the first payment dimension is obtained by associating the settlement revenue table with the owner payment instruction table and the owner payment instruction history table, and querying the owner payment instruction table and the owner payment instruction history table. The second payment dimension is obtained by associating the overall revenue report with the owner payment instruction table and the owner payment instruction history table, and querying the owner payment instruction table and the owner payment instruction history table. Based on the data corresponding to the first payment dimension and the second payment dimension, a daily settlement report is obtained, which can improve the efficiency of viewing settlement data generated by vehicle passage on highways.

[0074] Please see Figure 5 , Figure 5This is a schematic diagram of a highway traffic data recalculation device disclosed in an embodiment of this application. This highway traffic data recalculation device can be applied to the aforementioned electronic equipment. For example... Figure 5 As shown, the highway traffic data netting device 500 may include: a settlement acquisition module 501 and a report correspondence module 502.

[0075] The settlement acquisition module 501 is used to retrieve the owner settlement revenue table corresponding to the current settlement period from the database.

[0076] The corresponding module 502 is used to generate daily settlement reports based on the correspondence between the settlement income report and the overall income report for the current settlement period; the daily settlement reports change dynamically as payments are transferred.

[0077] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of this application. For example... Figure 6 As shown, the electronic device 600 may include:

[0078] Memory 601 storing executable program code;

[0079] Processor 602 coupled to memory 601;

[0080] The processor 602 calls the executable program code stored in the memory 601 to execute any of the highway traffic data netting methods disclosed in the embodiments of this application.

[0081] This application discloses a computer-readable storage medium storing a computer program, wherein when the computer program is executed by the processor, the processor implements any of the highway traffic data netting methods disclosed in this application.

[0082] This application discloses a computer program product, including a computer program, which, when executed by a processor, implements the methods described in the above embodiments.

[0083] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Those skilled in the art should also recognize that the embodiments described in the specification are optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0084] In the various embodiments of this application, it should be understood that the sequence number of each process does not necessarily imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0085] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; they can be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0086] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0087] If the integrated units described above are implemented as software functional units and sold or used as independent products, they can be stored in a computer-accessible memory. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several requests to cause a computer device (which can be a personal computer, server, or network device, specifically a processor in the computer device) to execute some or all of the steps of the methods described in the various embodiments of this application.

[0088] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, including read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-Erasable Programmable Read-Only Memory (EEPROM), compactdisc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium capable of carrying or storing data.

[0089] The foregoing has provided a detailed description of a highway traffic data netting method and related equipment disclosed in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and its core ideas. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for netting highway traffic data, characterized in that, Applied to electronic devices, the method includes: Retrieve the owner settlement revenue table corresponding to the current settlement period from the database; A daily settlement report is generated based on the correspondence between the owner's settlement revenue statement and the overall revenue statement for the current settlement period; the daily settlement report changes dynamically with payment and transfer. The owner settlement revenue table contains data on multiple owners; after retrieving the owner settlement revenue table corresponding to the current settlement period from the database, the method further includes: The owner data that meet the preset actual payment conditions in the owner settlement income table are summarized and an owner income record table is generated. Based on the aforementioned owner revenue record table, generate a corresponding owner transfer instruction table and owner transfer instruction history table; The step of generating a corresponding owner transfer instruction table and an owner transfer instruction history table based on the owner revenue record table includes: Based on the owner revenue record table and the overall revenue report, netting and settlement processing is performed to generate an owner netting data record table. The owner remittance instruction table is generated based on the data in the owner netting data record table that meets the preset remittance conditions; Multiple payment results are obtained from the owner payment instruction table, and the owner payment instruction history table is generated based on the multiple payment results. The step of generating a daily settlement report based on the correspondence between the owner's settlement revenue statement and the overall revenue report for the current settlement period includes: Based on the owner settlement revenue table, the owner transfer instruction table and the owner transfer instruction history table are associated, and queries are performed in the owner transfer instruction table and the owner transfer instruction history table to obtain the first transfer dimension; the first transfer dimension includes fields such as owner code, settlement date, fund system, card type, cross-province identifier, revenue amount, daily settlement serial number, netting batch number, instruction number, road segment code, and instruction generation date; The second payment dimension is obtained by associating the owner payment instruction table and the owner payment instruction history table with the overall revenue report, and querying the owner payment instruction table and the owner payment instruction history table; the second payment dimension includes fields such as owner code, revenue section code, actual amount received, netting batch number, settlement month, settlement date, payment start date, instruction number, and instruction generation date; The daily settlement report is obtained based on the data corresponding to the first and second payment dimensions, respectively.

2. The method for netting highway traffic data according to claim 1, characterized in that, Before generating the daily settlement report based on the correspondence between the owner's settlement revenue statement and the overall revenue statement corresponding to the current settlement period, the method further includes: Obtain owner settlement information; Based on the owner settlement information, the overall revenue report can be obtained.

3. The method for recalculating highway traffic data according to claim 1, characterized in that, The step of associating the owner settlement revenue statement with the owner transfer instruction table and the owner transfer instruction history table, and querying the owner transfer instruction table and the owner transfer instruction history table to obtain the first transfer dimension includes: Based on the owner code and daily settlement serial number in the owner settlement income table, the left link is connected to the owner income record table; Based on the netting batch number and owner code in the owner revenue record table, the left link is established to the owner netting data record table; Based on the road segment code and instruction number in the owner netting data record table, the data is left-linked to the owner reimbursement instruction table and the owner reimbursement instruction history table, and a query is performed in the owner reimbursement instruction table and the owner reimbursement instruction history table to obtain the first reimbursement dimension.

4. The method for recalculating highway traffic data according to claim 1, characterized in that, The step of associating the overall revenue report with the owner payment instruction table and the owner payment instruction history table, and querying the owner payment instruction table and the owner payment instruction history table to obtain the second payment dimension includes: Based on the netting batch number, owner code, settlement month, settlement date, and start date of payment transfer in the overall revenue report, the data is linked to the owner netting data record table. Based on the road segment code and instruction number in the owner netting data record table, the system is left-linked to the owner remittance instruction table and the owner remittance instruction history table, and queries are performed in the owner remittance instruction table and the owner remittance instruction history table to obtain the second remittance dimension.

5. An electronic device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor causes the processor to implement the highway traffic data netting method as described in any one of claims 1 to 4.

6. A highway traffic data reconciliation device, characterized in that, The highway traffic data netting device is used in the electronic device described in claim 5.

7. A storage medium storing a processor-executable program, characterized in that, The program executable by the processor is used, when executed by the processor, to perform the highway traffic data netting method according to any one of claims 1-4.

Images