CN112435049A

CN112435049A - Account checking data processing method and device, computer equipment and storage medium

Info

Publication number: CN112435049A
Application number: CN202011262559.3A
Authority: CN
Inventors: 梁永睿; 郝文静; 李媛; 张涛; 原帅
Original assignee: Dawning Information Industry Beijing Co Ltd; Dawning Information Industry Co Ltd
Current assignee: Dawning Information Industry Beijing Co Ltd; Dawning Information Industry Co Ltd
Priority date: 2020-11-12
Filing date: 2020-11-12
Publication date: 2021-03-02
Anticipated expiration: 2040-11-12
Also published as: CN112435049B

Abstract

The application relates to a reconciliation data processing method, a reconciliation data processing device, computer equipment and a storage medium. The method comprises the following steps: acquiring first reconciliation data from a resource supply end and second reconciliation data from a charging end; the first reconciliation data comprises at least one first operation identification, first resource occupation data and a unit charging numerical value corresponding to the unit resource; the second account checking data comprise at least one second operation identification, second resource occupation data and a second charging value; searching a second operation identifier corresponding to the first operation identifier to obtain a target identifier; and comparing the first resource occupation data corresponding to the first operation identifier with the second resource occupation data corresponding to the target identifier, and comparing the obtained first charging numerical value with the second charging numerical value corresponding to the target identifier to obtain a reconciliation result. By adopting the method, the problem of data matching between different systems or platforms can be solved.

Description

Account checking data processing method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a reconciliation data processing method and apparatus, a computer device, and a storage medium.

Background

With the development of computer technology, various resource suppliers providing high-performance computer clusters have appeared, and for computational resources provided by the resource suppliers, users need to pay for the resource suppliers according to the use conditions of the resources, for example, by using a SLURM pre-charging system. In the charging process, the provider and the user need to reconcile the previous resource usage and the cost to ensure the accuracy of the cost. However, in the conventional art, a method for settling and reconciling funds is generally a method applied to each bank, securities, and the like, which involves a fund transaction, and settlement and reconciliation are performed according to a specific transaction flow.

However, in the reconciliation data processing method in the conventional technology, the reconciliation mode is only performed in the same system or platform, but the data types of different systems or platforms are greatly different, and the conventional technology cannot solve the problem of data mismatch between different systems or different platforms.

Disclosure of Invention

In view of the above, it is necessary to provide a reconciliation data processing method, apparatus, computer device and storage medium capable of matching data between different systems or different platforms.

A reconciliation data processing method, the method comprising:

acquiring account checking operation data; the reconciliation operation data comprises first reconciliation data from a resource supply end and second reconciliation data from a charging end; the first reconciliation data comprises at least one first operation identification, first resource occupation data corresponding to each first operation identification and a unit charging numerical value corresponding to a unit resource; the second account checking data comprises at least one second operation identification, second resource occupation data corresponding to each second operation identification and a second charging value corresponding to each second operation identification;

for each first operation identification, searching a second operation identification corresponding to the first operation identification from the at least one second operation identification to obtain a target identification;

comparing first resource occupation data corresponding to the first operation identification with second resource occupation data corresponding to the target identification, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identification to obtain a reconciliation result; and the first charging numerical value is obtained based on the first resource occupation data corresponding to the first operation identification and the unit charging numerical value corresponding to the unit resource.

The reconciliation data processing method comprises the steps of respectively obtaining first reconciliation data from a resource supply end and second reconciliation data from a charging end, searching a second operation identification corresponding to each first operation identification from at least one second operation identification to obtain a target identification, comparing first resource occupation data corresponding to the first operation identification with second resource occupation data corresponding to the target identification, and comparing a first charging value obtained based on the first resource occupation data corresponding to the first operation identification and a unit charging value corresponding to the unit resource with a second charging value corresponding to the target identification to obtain a reconciliation result. Therefore, the first resource occupation data of the resource supply end can be compared with the second resource occupation data of the corresponding charging end, the first charging numerical value of the resource supply end is compared with the second charging numerical value of the corresponding charging end, the account checking result can solve the data matching problem between different systems or platforms such as the resource supply end and the charging end, and the basis is provided for ensuring the consistency of the resource occupation and the generated charge numerical value.

In one embodiment, the acquiring reconciliation job data includes:

and acquiring first reconciliation data and second reconciliation data in a first time interval to obtain the reconciliation operation data.

In one embodiment, the comparing the first resource occupation data corresponding to the first job identifier with the second resource occupation data corresponding to the target identifier, and comparing the obtained first charging value with the second charging value corresponding to the target identifier to obtain the reconciliation result includes:

dividing the first time interval to obtain at least one second time interval;

dividing the first resource occupation data, the second resource occupation data and the second charging numerical value according to the second time interval to obtain corresponding first target resource occupation data, second target resource occupation data and target charging numerical value;

executing the account checking task, wherein the executing process of the account checking task comprises the following steps: and comparing first target resource occupation data corresponding to the first operation identification with second target resource occupation data corresponding to the target identification, and comparing the first charging value with a target charging value corresponding to the target identification to obtain the reconciliation result.

In the embodiment, the first reconciliation data and the second reconciliation data in the first time interval are acquired to obtain the reconciliation operation data; and dividing the first time interval to obtain at least one second time interval, providing a basis for subsequently dividing huge account checking data into account checking operation data with smaller magnitude, and respectively executing account checking tasks corresponding to the second time intervals. Therefore, reconciliation can be performed in batches, the condition that resources occupy too much in the one-time reconciliation process is reduced, and the overall performance of reconciliation data processing is improved.

In one embodiment, the performing the reconciliation task includes:

acquiring a target time interval corresponding to the target account checking task; the target account checking task is a current on-going account checking task;

detecting whether a part of the second time interval and the target time interval are overlapped or not;

and if not, executing the account checking task corresponding to the second time interval.

In the embodiment, a target time interval corresponding to the target reconciliation task is obtained; the target account checking task is a current account checking task; detecting whether the second time interval and the target time interval have overlapped parts; and if not, executing the account checking task corresponding to the second time interval. Therefore, when account checking is carried out, only one account checking task is guaranteed to be executed at a time, concurrent read-write data conflict is avoided, and accuracy of account checking results is guaranteed.

In one embodiment, the comparing the first resource occupation data corresponding to the first job identifier with the second resource occupation data corresponding to the target identifier, and comparing the obtained first charging value with the second charging value corresponding to the target identifier to obtain a reconciliation result includes:

respectively determining account checking results corresponding to each first operation identification to obtain at least one account checking result corresponding to the at least one first operation identification;

and combining the at least one reconciliation result to obtain a target reconciliation result.

In one embodiment, the first resource occupancy data includes a corresponding first work resource, first work machine time; the second resource occupation data comprises corresponding second operation resources and second operation machine time;

comparing first resource occupation data corresponding to the first operation identifier with second resource occupation data corresponding to the target identifier, and comparing a first charging value with a second charging value corresponding to the target identifier to obtain a reconciliation result, including:

comparing a first operation resource corresponding to the first operation identifier with a second operation resource corresponding to the target identifier, and obtaining a charging resource comparison result when comparing a first operation machine corresponding to the first operation identifier with a second operation machine corresponding to the target identifier;

determining the first charging value according to the first operating resource, the first operating machine time and the unit charging value corresponding to the unit resource;

comparing the first charging value with the second charging value to obtain a charging value comparison result;

and combining the charging resource comparison result and the charging numerical value comparison result to obtain the account checking result.

In the above embodiment, the first job resource corresponding to the first job identifier is compared with the second job resource corresponding to the target identifier, and when the first job machine corresponding to the first job identifier is compared with the second job machine corresponding to the target identifier, a charging resource comparison result is obtained; determining a first charging value according to the first operating resource, the first operating machine time and the unit charging value corresponding to the unit resource; comparing the first charging value with the second charging value to obtain a charging value comparison result; and combining the charging resource comparison result and the charging numerical value comparison result to obtain an account checking result. The obtained account checking result comprises the comparison of the resource occupation situation and the comparison of the charging numerical value, so that the account checking result can reflect whether the resource occupation situation and the generated cost respectively correspond or not at the same time, and dual data guarantee is provided for ensuring the consistency of data matching between different systems or platforms such as a resource supply end and a charging end.

In one embodiment, each first job identifier includes at least one corresponding charging switch, and the charging switch is configured to identify a charging state corresponding to the first job identifier, where the charging state includes three states, namely charging, non-charging, and unknown charging state;

the comparing the first resource occupation data corresponding to the first operation identifier with the second resource occupation data corresponding to the target identifier, and comparing the obtained first charging value with the second charging value corresponding to the target identifier to obtain a reconciliation result includes:

and when the charging state is charging, executing the steps of comparing the first resource occupation data corresponding to the first operation identification with the second resource occupation data corresponding to the target identification, and comparing the obtained first charging numerical value with the second charging numerical value corresponding to the target identification to obtain a reconciliation result.

In the above embodiment, when the charging status is charging, the step of comparing the first resource occupation data corresponding to the first job identifier with the second resource occupation data corresponding to the target identifier and comparing the obtained first charging value with the second charging value corresponding to the target identifier is performed to obtain the reconciliation result. The phenomenon that charging is missed when the charging state is charging can be avoided, or the phenomenon that the charging is mistakenly charged when the charging state is charging-free and the charging state is unknown is avoided. Whether the resource occupation corresponds to the generated cost is reflected, and a basis is provided for ensuring the consistency of the resource occupation and the generated cost.

A reconciliation data processing apparatus, the apparatus comprising:

the data acquisition module is used for acquiring account checking operation data; the reconciliation operation data comprises first reconciliation data from a resource supply end and second reconciliation data from a charging end; the first reconciliation data comprises at least one first operation identification, first resource occupation data corresponding to each first operation identification and a unit charging numerical value corresponding to a unit resource; the second account checking data comprises at least one second operation identification, second resource occupation data corresponding to each second operation identification and a second charging value corresponding to each second operation identification;

the job identifier searching module is used for searching a second job identifier corresponding to the first job identifier from the at least one second job identifier for each first job identifier to obtain a target identifier;

and the account checking module is used for comparing first resource occupation data corresponding to the first operation identifier with second resource occupation data corresponding to the target identifier, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identifier to obtain an account checking result. A computer device comprising a memory storing a computer program and a processor implementing the steps of any of the methods described above when the processor executes the computer program.

A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any of the above.

According to the reconciliation data processing method, the device, the computer equipment and the storage medium, the first reconciliation data from the resource supply end and the second reconciliation data from the charging end are respectively obtained, for each first job identification, the second job identification corresponding to each first job identification is searched from at least one second job identification to obtain the target identification, the first resource occupation data corresponding to the first job identification is compared with the second resource occupation data corresponding to the target identification, and the first charging value obtained based on the first resource occupation data corresponding to the first job identification and the unit charging value corresponding to the unit resource is compared with the second charging value corresponding to the target identification to obtain the reconciliation result. Therefore, the first resource occupation data of the resource supply end and the second resource occupation data of the corresponding charging end can be compared, the first charging numerical value of the resource supply end and the second charging numerical value of the corresponding charging end are compared, the account checking result can solve the problem of data matching between different systems or platforms such as the resource supply end and the charging end, and a basis is provided for data matching between different systems or platforms.

Drawings

FIG. 1 is a diagram of an application environment of a reconciliation data processing method in one embodiment;

FIG. 2 is a flow diagram illustrating a method for reconciliation data processing in one embodiment;

FIG. 3 is a schematic flow chart diagram illustrating one possible implementation of step S300 in one embodiment;

FIG. 4 is a schematic flow chart diagram illustrating one possible implementation of step S300 in one embodiment;

fig. 5 is a schematic diagram of a reconciliation data processing method based on the SLURM pre-charging system in an embodiment;

fig. 6 is a flow chart of a reconciliation data processing method based on the SLURM pre-charging system;

FIG. 7 is a schematic flow chart diagram illustrating an exemplary embodiment of determining a reconciliation time range in an automatic reconciliation manner;

FIG. 8 is a flowchart illustrating an exemplary embodiment of determining a reconciliation time range in a manual reconciliation;

fig. 9 is a flowchart illustrating a reconciliation data processing method based on the SLURM pre-charging system;

FIG. 10 is a flow diagram illustrating one possible embodiment for reconciling a plurality of jobs one by one;

FIG. 11 is a flow diagram of one possible embodiment of a single job reconciliation;

FIG. 12 is a block diagram showing the configuration of a reconciliation apparatus in one embodiment;

FIG. 13 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The reconciliation data processing method provided by the application can be applied to the application environment shown in FIG. 1. Wherein the terminal 102 communicates with the server 104 via a network. The terminal 102 obtains first reconciliation data from the resource supply end and second reconciliation data from the charging end respectively, searches a second operation identification corresponding to each first operation identification from at least one second operation identification to obtain a target identification, compares first resource occupation data corresponding to the first operation identification in the first reconciliation data corresponding to the first operation identification with second resource occupation data corresponding to the target identification, and compares a first charging numerical value obtained based on the first resource occupation data corresponding to the first operation identification and a unit charging numerical value corresponding to the unit resource with the second charging numerical value corresponding to the target identification to obtain a reconciliation result. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.

In an embodiment, as shown in fig. 2, a reconciliation data processing method is provided, which is described by taking the application of the method to the terminal in fig. 1 as an example, and includes the following steps:

step S100, obtaining account checking operation data; the reconciliation operation data comprises first reconciliation data from a resource supply end and second reconciliation data from a charging end; the first reconciliation data comprises at least one first operation identification, first resource occupation data corresponding to each first operation identification and a unit charging numerical value corresponding to the unit resource; the second account checking data comprises at least one second operation identification, second resource occupation data corresponding to each second operation identification and a second charging value corresponding to each second operation identification.

Step S200, for each first job identifier, searching for a second job identifier corresponding to the first job identifier from at least one second job identifier to obtain a target identifier.

Step S300, comparing first resource occupation data corresponding to the first operation identification with second resource occupation data corresponding to the target identification, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identification to obtain a reconciliation result; the first charging numerical value is obtained based on the first resource occupation data corresponding to the first operation identification and the unit charging numerical value corresponding to the unit resource.

The resource supply end is an end providing computer resources, and may be a terminal device, a server, a High Performance Computing (HPC), and the like. The Gridview is used as one of HPC cloud platforms, integrates simulation calculation and industrial design, unifies portals, centralizes data management, simplifies industrial design work flow, provides one-stop service for users, can realize scheduling distribution, job submission, job management, state monitoring, statistics and accounting and the like of high-performance computing resources, supports installation of various types of application software, such as manufacturing design, scientific simulation calculation and the like, and can provide a cluster integration solution. The charging terminal refers to an electronic charging system terminal, such as GOLD charging system or SLURM-based pre-charging system. The GOLD billing system is an open source billing system for tracking and managing resource usage on high performance computers. The SLURM-based pre-charging system is a pre-charging system of an SLURM scheduling system, integrates the SLURM scheduling system with a GOLD charging system, realizes the machine-hour management of a user, converts the using resource condition of the operation into machine-hour pre-charging and post-charging of the machine-hour operation, and controls whether the operation can be operated according to the current machine-hour condition of the user.

Specifically, data such as resource usage and resource price are stored in the resource supply side (e.g., Gridview platform), and data such as resource usage and job fee generated by resource usage are stored in the billing side (e.g., SLURM-based pre-billing system). The method comprises the steps of respectively obtaining at least one first operation identification, first resource occupation data corresponding to each first operation identification and a unit charging value corresponding to a unit resource from a resource supply end, and obtaining at least one second operation identification, second resource occupation data corresponding to each second operation identification and a second charging value corresponding to each second operation identification from a charging end. After the account checking operation data is obtained, for each first operation identification, according to the first operation identification, searching a second operation identification corresponding to each first operation identification from at least one second operation identification, and determining the searched second operation identification corresponding to the first operation identification as a target identification. And comparing first resource occupation data corresponding to the first operation identification with second resource occupation data corresponding to the target identification, comparing a first charging numerical value obtained based on the first resource occupation data corresponding to the first operation identification and a unit charging numerical value corresponding to the unit resource with a second charging numerical value corresponding to the target identification, and determining the comparison result as an account checking result.

In one embodiment, step S100, acquiring reconciliation job data, includes:

and acquiring first reconciliation data and second reconciliation data in a first time interval to obtain reconciliation operation data.

The first time interval is a preset time interval, for example, a day, a week, a month, or a year is different, and a certain time interval is mainly set for reconciliation so as to determine data used for reconciliation, and optionally, the first time interval may be from 00:00:00 in the previous day to 00:00:00 in the next day.

Specifically, first reconciliation data and second reconciliation data in a first time interval are acquired, and the first reconciliation data and the second reconciliation data in the time interval are determined as reconciliation job data. The reconciliation data is acquired in a time-limited mode, on one hand, the data used for the reconciliation is convenient to determine, and on the other hand, a starting time and a terminating time are determined for the reconciliation to determine a reconciliation range.

Optionally, as shown in fig. 3, which is a schematic flow chart of an implementation manner of step S300, the method includes the following steps:

step S311, the first time interval is divided to obtain at least one second time interval.

Step S312, according to the second time interval, the first resource occupation data, the second resource occupation data, and the second charging value are divided to obtain the corresponding first target resource occupation data, the second target resource occupation data, and the target charging value.

Step S313, executing a reconciliation task, wherein the execution process of the reconciliation task comprises the following steps: and comparing the first target resource occupation data corresponding to the first operation identification with the second target resource occupation data corresponding to the target identification, and comparing the first charging numerical value with the target charging numerical value corresponding to the target identification to obtain a reconciliation result.

The second time interval is a time interval smaller than the first time interval, and is mainly a time interval set for reconciliation so as to determine data used for reconciliation in batches.

Specifically, the first time interval is divided into a plurality of second time intervals, for example, 00:00: 00:00 of the previous day to 00:00: 00:00 of the next day are divided into (00: 00:00,00:01:00], (00:01:00,00:02:00, 00:023:00, 00:00:00 of the next day.) after the first time interval is divided into a plurality of second time intervals, the reconciliation task is executed one by one in each second time interval, the first target resource occupation data corresponding to the first job identifier is compared with the second target resource occupation data corresponding to the target identifier, and the first billing value is compared with the target billing value corresponding to the target identifier, so as to obtain the reconciliation result.

In one embodiment, one possible implementation of step S312 includes:

acquiring a target time interval corresponding to the target account checking task; the target account checking task is a current account checking task; detecting whether the second time interval and the target time interval have overlapped parts; and if not, executing the account checking task corresponding to the second time interval.

The target time interval is a time range in which the reconciliation task is currently executed, for example, a time range corresponding to reconciliation job data from the resource supply end and the charging end used by the reconciliation task.

Specifically, if a plurality of different reconciliation tasks with time overlaps are started, the same reconciliation operation data at the time overlaps can be processed at the same time, and in order to avoid concurrent read-write data conflicts, it is necessary to ensure that the reconciliation time ranges of the currently-performed reconciliation tasks cannot overlap, and therefore, before starting one reconciliation task, it is necessary to detect whether the currently-performed reconciliation task exists. Specifically, a target time interval corresponding to the current account checking task is obtained, whether an overlapped part exists between the second time interval and the target time interval or not is detected, if yes, the account checking process is quitted to wait, and if no on-going account checking task exists, the account checking is carried out according to the account checking process until an account checking result is obtained.

Optionally, detecting whether there is an overlapping portion between the second time interval and the target time interval; and if the target time interval does not exist, determining the second time interval as a target time interval, and executing the reconciliation task corresponding to the second time interval.

Specifically, after the account checking task is completed once, the target time interval determined by the second time interval is deleted. The time interval overlapping with the subsequent reconciliation task is avoided, and the concurrent read-write conflict is avoided.

In one embodiment, the method of step S300 includes:

respectively determining account checking results corresponding to each first operation identification to obtain at least one account checking result corresponding to at least one first operation identification; and combining at least one reconciliation result to obtain a target reconciliation result.

Specifically, the reconciliation data includes a plurality of first job identifiers, each first job identifier corresponds to a second job identifier, and the second job identifier corresponding to the first job identifier can be regarded as a target identifier, so that each first job identifier corresponds to a small reconciliation result, and each first job identifier corresponds to a small reconciliation result and is combined to obtain a final reconciliation result.

Optionally, as shown in fig. 4, which is a schematic flow chart of an implementation manner of step S300, the method includes the following steps:

step S321, comparing the first job resource corresponding to the first job identifier with the second job resource corresponding to the target identifier, and obtaining a charging resource comparison result when comparing the first job machine corresponding to the first job identifier with the second job machine corresponding to the target identifier.

Step S322, according to the first operating resource, the first operating machine time and the unit charge value corresponding to the unit resource, determining a first charge value.

Step S323, comparing the first billing value with the second billing value to obtain a billing value comparison result.

Step S324, the charging resource comparison result and the charging value comparison result are combined to obtain an account checking result.

The first resource occupation data comprises corresponding first operating resources and first operating machine time; the second resource occupation data includes a corresponding second work resource and a second work machine time.

Specifically, the cost of resource occupation is generally determined by the amount of resources occupied by a job and the occupied time, and the cost generally increases as the occupied resource amount increases and the occupied time increases. Therefore, when checking account, the resource occupation condition and the occupation time need to be compared respectively. Specifically, when the resource occupation condition is compared, the first job resource corresponding to the first job identifier and the second job resource corresponding to the target identifier need to be compared, and when the first job machine corresponding to the first job identifier and the second job machine corresponding to the target identifier are compared, the charging resource comparison result is obtained. When the occupied time of the resource is compared, a corresponding first charging value (cost) needs to be determined according to the first operating resource, the first operating machine time and the unit charging value (unit price) corresponding to the unit resource, for example, the first operating resource is 3 unit spaces, the first operating machine time is 2 hours, the resource price of the unit space is 0.5 yuan per hour, and the occupied time (cost) of the resource is 3 × 2 × 0.5 yuan — 3 yuan. And finally, determining the charging resource comparison result and the charge comparison result of the charging numerical value as a reconciliation result.

In one embodiment, the method of step S300 includes:

and when the charging state is charging, comparing first resource occupation data corresponding to the first operation identifier with second resource occupation data corresponding to the target identifier, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identifier to obtain a reconciliation result.

And setting a charging switch for each first operation identifier, and setting a corresponding charging state according to the actual charging condition. Each first operation identification comprises at least one corresponding charging switch, and the charging switch is used for identifying charging states corresponding to the first operation identification and comprises three states of charging, non-charging and unknown charging states.

Specifically, the resource provider includes a plurality of first job identifiers therein, but the plurality of first job identifiers do not necessarily all use the resource provided by the resource provider. There may be situations where a user has initiated a resource usage request to a resource provider based on a first job identification, but the task scheduling system has not provided resources to the user for that first job identification. At this time, the resource provider may record the first job identifier, but the first job identifier does not participate in the charging, or the charging status of the first job identifier is unknown due to an abnormal operation such as a manual operation, which is generally not charged. When the charging state is charging, the steps of comparing the first resource occupation data corresponding to the first operation identification with the second resource occupation data corresponding to the target identification and comparing the first charging numerical value with the second charging numerical value corresponding to the target identification are executed to obtain a reconciliation result, so that the phenomenon that charging is missed when the charging state is charging or the phenomenon that charging is mistaken when the charging state is charging-free and unknown is avoided.

Optionally, when the charging status is "charging status unknown", the resource occupation data is obtained again from the charging status unknown and the charging terminal, respectively, the charging status of the first operation identifier occupying the specific resource is modified to "charging", and the charging status of the first operation identifier not occupying the specific resource is modified to "no charging". And executing the steps of comparing first resource occupation data corresponding to the first operation identification with second resource occupation data corresponding to the target identification, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identification until an account checking result is obtained.

In a specific embodiment, as shown in fig. 5, a schematic diagram of a reconciliation data processing method based on an SLURM pre-charging system is shown. The realization of the account checking data processing method based on the SLURM pre-charging system needs to use a Gridview platform as a resource supply end and an SLURM-based pre-charging system as a basis, wherein a charging system in the SLURM-based pre-charging system is a GOLD charging system. The account checking task system comprises a Gridview management node, an SLURM database, a Gridview data table and a GOLD data table. Specifically, the reconciliation task (reconciliation service) is deployed at the Gridview management node. The Gridview management node can communicate with the Gridview data table, the GOLD data table and the SLURM management node, the Gridview management node can acquire the Gridview data table and the GOLD data table through communication with the Gridview data table and the GOLD data table, the operation information of the SLURM database is acquired through communication with the SLURM management node, the acquired operation information of the Gridview data table, the GOLD data table and the SLURM database is used for checking accounts, and the checking result is stored in the Gridview data table.

Fig. 6 is a schematic flow chart of a reconciliation data processing method based on the SLURM pre-charging system, and as shown in fig. 6, different reconciliation modes (automatic reconciliation and manual reconciliation) only have a difference in a reconciliation time range, which is specifically embodied in an update time stamp step of a total flow and a sub-flow of "determining a reconciliation time range". Firstly, determining a reconciliation time range, checkStartTime and checkEndTime, wherein the checkStartTime represents the starting time of the present reconciliation total process, and the checkEndTime represents the ending time of the present reconciliation total process. In view of the fact that starting a plurality of reconciliation tasks involves processing the same data table at the same time, read-write conflicts may occur, and in order to avoid concurrent read-write data conflicts, the reconciliation time ranges of the ongoing reconciliation tasks may be limited so that the reconciliation time ranges do not overlap. Therefore, before the account checking, whether the time range of the ongoing account checking task is overlapped with the time range of the account checking task needs to be checked, if so, the account checking task is ended, and after the existing account checking task is ended, the account checking task is restarted again. And if the two items are not overlapped, recording the time range of the account checking task, and starting account checking.

It should be noted that, because the reconciliation data volume of the total process may be large and affect the reconciliation performance, the reconciliation data is taken out in batches for reconciliation with 1 hour as a unit. startTimeFor1H indicates the start time corresponding to the batch reconciliation data, and endTimeFor1H indicates the end time corresponding to the batch reconciliation data. According to startTimeFor1H and endTimeFor1H, the reconciliation data in 1 hour is obtained and the reconciliation is carried out hour by hour. And after the whole account checking is finished, deleting the time range of the account checking task and finishing the account checking task.

It should be noted that, when starting a plurality of reconciliation tasks, the same data table is processed at the same time, and in order to avoid concurrent read-write data conflicts, the reconciliation time ranges of the ongoing reconciliation tasks can be limited, so that the reconciliation time ranges are not overlapped. For example, a global variable may be used to store the reconciliation time range of the ongoing reconciliation task, and when each reconciliation task is started, it is first checked whether the task overlaps with the reconciliation time range of the ongoing reconciliation task, and if so, the task is directly exited; if not, the time range of the task is added to the global variable List, and then the account checking is started. And after the account checking task finishes account checking, deleting the account checking time range of the task from all the variable Lists.

Fig. 7 is a schematic flowchart of an implementation manner of determining a reconciliation time range in an automatic reconciliation manner, as shown in fig. 7, if an automatic reconciliation task is automatically executed every morning at 2:00, a data time range of the reconciliation is normally within a time range from 00:00: 00:00 of a previous day to 00:00: 00:00 of a next day. Firstly, whether an automatic account checking task is executed or not is detected, if yes, the account checking is finished, if not, an automatic account checking timestamp is obtained from a check. The timestamp automatically checks the newly added data on the same day to ensure that all operations and deduction data in the system completely complete at least one check according to the time sequence. The automatic reconciliation process involves reading and modifying timestamps, and therefore only one automatic reconciliation task is allowed to execute at the same time. If the time of the timestamp is before today 0, the timestamp is considered to be a valid timestamp, the timestamp is taken as the accounting start time checkStartTime (start time) of this time, today 00:00:00 is taken as the accounting end time checkEndTime (end time) of this time, and the accounting is automatically performed according to the determined start time and the determined end time. Fig. 8 is a schematic flow chart of an implementable embodiment for determining a reconciliation time range in a manual reconciliation manner, as shown in fig. 8, a timestamp is not used for manual reconciliation, a reconciliation start time and an accounting end time set by a user are obtained from a front end, whether the start time is less than a current time is checked to ensure that corresponding reconciliation data exists, and the accounting end time is half an hour earlier than the current time to ensure sufficient storage of the reconciliation data and avoid data inaccuracy caused by hysteresis of the reconciliation data storage. And then, setting the time acquired by the front end as the starting time checkStartTime and the ending time checkEndTime of the account checking, and performing the account checking.

Fig. 9 is a schematic flow chart of a reconciliation data processing method based on an SLURM pre-charging system, and as shown in fig. 9, in the reconciliation data processing method based on the SLURM pre-charging system, when reconciliation is performed within a small range of time (e.g., 1 hour), relevant data required for reconciliation within 1 hour needs to be acquired. Firstly, checking whether a Slurm service database and a Gridview database are normal or not, if not, acquiring data required by account checking, and directly quitting to finish the account checking. And after the checking is normal, connecting a Gridview database, and after the Gridview database is successfully connected, respectively querying the operation information in a certain hour from three data sources (an SLURM task scheduling system, the Gridview database and a GOLD database) according to the operation ending time. The query of the job information needs to ensure that the query conditions are completely consistent, otherwise, the data difference caused by the difference of the query conditions is treated as an error in the reconciliation process, so that the reconciliation result is inaccurate. And performing subsequent account checking according to the data inquired from the SLURM task scheduling system, the Gridview database and the GOLD database. And the data query is carried out on the premise of ensuring the normal work of the corresponding service, so that the error rate of the data can be reduced, and the accuracy of the account checking data is improved.

Fig. 10 is a flow chart of an implementation mode of checking accounts of a plurality of jobs one by one, and fig. 11 is a flow chart of an implementation mode of checking accounts of a single job. The job ID (jobId) and the job end time (endTime) uniquely identify one job, and each job is checked in sequence until the jobs in the current hour are all checked. As shown in fig. 10, the reconciliation object acctcheckjobb object of a single job contains all the information required for reconciliation. Firstly, taking out a job (AcctCheckJob object), judging the charging state of the job, checking account when a single job fee deducting machine exists if the charging state value has an open state, and checking account of the next job after the account checking of all jobs in the current hour is finished. As shown in fig. 11, if the number of records of the job in the scheduler is not equal to 1, it is determined that the scheduler number of records is abnormal, and the reconciliation is finished. If the number of records in Gridview is more than that of the scheduler records, and the job ID (jobmanager _ ID) of the job record in Gridview is the same, the method can be judged to be repeatedly put in storage. And the job ID and the job end time uniquely identify one job, and each job is checked in sequence until the jobs in the current hour are all checked. The repeated warehousing detection of fig. 11 can avoid repeated account checking of account checking data of the same job, and avoid account checking errors caused by repeated account checking.

Alternatively, if there are multiple records in the GridView table for a job, each record containing a billing switch status, the value of each billing switch may be different. From the practical situation, the situation that a plurality of records exist in Gridview for the job with the same job ID and the same end time rarely occurs, but the account checking system is used as an error correction system and should cover all abnormal situations as much as possible. Therefore, accurate billing according to the billing switch value is required. Illustratively, the value of the charging switch is null, which indicates that the charging switch record of the job is not queried when the record is put in storage. The operation warehousing and fee deduction are two independent processes, the charging switch is not checked during warehousing, and whether the charging switch record is checked during fee deduction cannot be determined, so that the fee deduction condition of the record cannot be judged. Therefore, when the charging switch value is empty in one operation, the account checking in the fee deducting machine is not carried out, and error data is recorded. The charging switch value of true represents that the operation is charged, false represents that the operation is not charged, and unknown represents that the charging switch state is unknown during the operation, the operation is not allowed, and the operation is not charged. If a record with the value of the charging switch being true exists in one operation, a GOLD fee deduction record should exist, so that the number billingCountInGV of the record with the value of the charging switch being true is counted, and the fee deduction machine time account is checked. If all the billing switches are false or unknown, there should be no record of deduction in GOLD. In the presence of nown, it is also counted as an error record in the Gridview database.

Optionally, for the job with the value of the charging switch being true, performing single job fee deduction machine time reconciliation. The comparison between the Gridview data table and the data of the working withholding time and the real withholding time in the GOLD is carried out when the fee withholding time is compared, and if the record is 0, the comparison of the numerical values of the fee withholding time is not needed. If no record is 0, parameters such as resource unit price, number, rate, operation running time and the like of each record in Gridview are calculated according to a formula of charging time charge (CPU unit price + GPU unit price) rate running time, and the time to be charged can be calculated. And if the Gridview has records and the GOLD has no records, querying some error record files in the charging system. Optionally, for job records in which the time of machine deduction in Gridview is inconsistent with the time of real machine deduction in GOLD, performing machine-time parameter reconciliation. Alternatively, if a job is manually deducted by means of a command, it is likely that the end time parameter of the job is not recorded, and this part of the deduction time is called the surcharge time. In the manual fee deduction mode, because of lack of end time, extra fee deduction machine time data cannot be found out in the previous 'acquiring account checking operation information' process, which is carried out in one hour unit, in order to keep consistency of data before and after, extra fee deduction machine time data is separately processed in the process and is stored in a separate data table in one hour unit.

In the above embodiment, the resource price of the resource supply end is compared with the operation cost of the corresponding charging end, and the reconciliation result can reflect whether the resource occupation corresponds to the generated cost, so as to provide a basis for ensuring the consistency of the resource occupation and the generated cost. Meanwhile, account checking time can be subdivided, account checking can be performed in batches, the situation that resources occupy too much in the one-time account checking process is reduced, and account checking performance is improved. And one account checking service can be ensured to only execute one account checking task, so that read-write data conflict is avoided, and the accuracy of the account checking result is ensured. The phenomenon that charging is missed when the charging state is charging or the phenomenon that the charging is mistaken when the charging state is not charging and the charging state is unknown can be avoided.

It should be understood that although the various steps in the flow charts of fig. 2-11 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-11 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.

In one embodiment, as shown in fig. 12, there is provided a reconciliation apparatus comprising: data acquisition module 121, job identification lookup module 122, and reconciliation module 123, wherein:

a data acquisition module 121, configured to acquire reconciliation job data; the reconciliation operation data comprises first reconciliation data from a resource supply end and second reconciliation data from a charging end; the first reconciliation data comprises at least one first operation identification, first resource occupation data corresponding to each first operation identification and a unit charging numerical value corresponding to the unit resource; the second account checking data comprise at least one second operation identification, second resource occupation data corresponding to each second operation identification and a second charging value corresponding to each second operation identification;

the job identifier searching module 122 is configured to, for each first job identifier, search, from at least one second job identifier, a second job identifier corresponding to the first job identifier to obtain a target identifier;

the reconciliation module 123 is configured to compare first resource occupation data corresponding to the first job identifier with second resource occupation data corresponding to the target identifier, and compare the obtained first charging value with a second charging value corresponding to the target identifier to obtain a reconciliation result; the first charging numerical value is obtained based on the first resource occupation data corresponding to the first operation identification and the unit charging numerical value corresponding to the unit resource.

In one embodiment, the data acquiring module 121 is further configured to acquire first reconciliation data and second reconciliation data in a first time interval, so as to obtain reconciliation job data.

In one embodiment, the reconciliation module 123 is further configured to divide the first time interval to obtain at least one second time interval; dividing the first resource occupation data, the second resource occupation data and the second charging numerical value according to a second time interval to obtain corresponding first target resource occupation data, second target resource occupation data and target charging numerical values; and executing the account checking task, wherein the executing process of the account checking task comprises the following steps: and comparing the first target resource occupation data corresponding to the first operation identification with the second target resource occupation data corresponding to the target identification, and comparing the first charging numerical value with the target charging numerical value corresponding to the target identification to obtain a reconciliation result.

In one embodiment, the reconciliation module 123 is further configured to obtain a target time interval corresponding to the target reconciliation task; the target account checking task is a current account checking task; detecting whether the second time interval and the target time interval have overlapped parts; and if not, executing the account checking task corresponding to the second time interval.

In an embodiment, the reconciliation module 123 is further configured to respectively determine a reconciliation result corresponding to each first job identifier, and obtain at least one reconciliation result corresponding to at least one first job identifier; and combining at least one reconciliation result to obtain a target reconciliation result.

In one embodiment, the reconciliation module 123 is further configured to compare the first job resource corresponding to the first job identifier with the second job resource corresponding to the target identifier, and obtain a charging resource comparison result when comparing the first job machine corresponding to the first job identifier with the second job machine corresponding to the target identifier; determining a first charging value according to the first operating resource, the first operating machine time and the unit charging value corresponding to the unit resource; comparing the first charging value with the second charging value to obtain a charging value comparison result; and combining the charging resource comparison result and the charging numerical value comparison result to obtain an account checking result.

In an embodiment, the reconciliation module 123 is further configured to, when the charging status is charging, perform, when the charging status is charging, a step of comparing first resource occupation data corresponding to the first job identifier with second resource occupation data corresponding to the target identifier, and comparing the obtained first charging value with a second charging value corresponding to the target identifier to obtain a reconciliation result.

For specific limitations of the reconciliation device, reference may be made to the above limitations on the reconciliation data processing method, which will not be described herein again. The modules in the reconciliation device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 13. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a reconciliation data processing method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 13 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:

acquiring account checking operation data; the reconciliation operation data comprises first reconciliation data from a resource supply end and second reconciliation data from a charging end; the first reconciliation data comprises at least one first operation identification, first resource occupation data corresponding to each first operation identification and a unit charging numerical value corresponding to the unit resource; the second account checking data comprise at least one second operation identification, second resource occupation data corresponding to each second operation identification and a second charging value corresponding to each second operation identification;

for each first job identification, searching a second job identification corresponding to the first job identification from at least one second job identification to obtain a target identification;

comparing first resource occupation data corresponding to the first operation identification with second resource occupation data corresponding to the target identification, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identification to obtain a reconciliation result; the first charging numerical value is obtained based on the first resource occupation data corresponding to the first operation identification and the unit charging numerical value corresponding to the unit resource.

In one embodiment, the processor, when executing the computer program, further performs the steps of: and acquiring first reconciliation data and second reconciliation data in a first time interval to obtain reconciliation operation data.

In one embodiment, the processor, when executing the computer program, further performs the steps of: dividing the first time interval to obtain at least one second time interval; dividing the first resource occupation data, the second resource occupation data and the second charging numerical value according to a second time interval to obtain corresponding first target resource occupation data, second target resource occupation data and target charging numerical values; and executing the account checking task, wherein the executing process of the account checking task comprises the following steps: and comparing the first target resource occupation data corresponding to the first operation identification with the second target resource occupation data corresponding to the target identification, and comparing the first charging numerical value with the target charging numerical value corresponding to the target identification to obtain a reconciliation result.

In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a target time interval corresponding to the target account checking task; the target account checking task is a current account checking task; detecting whether the second time interval and the target time interval have overlapped parts; and if not, executing the account checking task corresponding to the second time interval.

In one embodiment, the processor, when executing the computer program, further performs the steps of: respectively determining account checking results corresponding to each first operation identification to obtain at least one account checking result corresponding to at least one first operation identification; and combining at least one reconciliation result to obtain a target reconciliation result.

In one embodiment, the processor, when executing the computer program, further performs the steps of: comparing a first operation resource corresponding to the first operation identifier with a second operation resource corresponding to the target identifier, and obtaining a charging resource comparison result when comparing the first operation machine corresponding to the first operation identifier with the second operation machine corresponding to the target identifier; determining a first charging value according to the first operating resource, the first operating machine time and the unit charging value corresponding to the unit resource; comparing the first charging value with the second charging value to obtain a charging value comparison result; and combining the charging resource comparison result and the charging numerical value comparison result to obtain an account checking result.

In one embodiment, the processor, when executing the computer program, further performs the steps of: and when the charging state is charging, comparing first resource occupation data corresponding to the first operation identifier with second resource occupation data corresponding to the target identifier, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identifier to obtain a reconciliation result.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:

In one embodiment, the computer program when executed by the processor further performs the steps of: and acquiring first reconciliation data and second reconciliation data in a first time interval to obtain reconciliation operation data.

In one embodiment, the computer program when executed by the processor further performs the steps of: dividing the first time interval to obtain at least one second time interval; dividing the first resource occupation data, the second resource occupation data and the second charging numerical value according to a second time interval to obtain corresponding first target resource occupation data, second target resource occupation data and target charging numerical values; and executing the account checking task, wherein the executing process of the account checking task comprises the following steps: and comparing the first target resource occupation data corresponding to the first operation identification with the second target resource occupation data corresponding to the target identification, and comparing the first charging numerical value with the target charging numerical value corresponding to the target identification to obtain a reconciliation result.

In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a target time interval corresponding to the target account checking task; the target account checking task is a current account checking task; detecting whether the second time interval and the target time interval have overlapped parts; and if not, executing the account checking task corresponding to the second time interval.

In one embodiment, the computer program when executed by the processor further performs the steps of: respectively determining account checking results corresponding to each first operation identification to obtain at least one account checking result corresponding to at least one first operation identification; and combining at least one reconciliation result to obtain a target reconciliation result.

In one embodiment, the computer program when executed by the processor further performs the steps of: comparing a first operation resource corresponding to the first operation identifier with a second operation resource corresponding to the target identifier, and obtaining a charging resource comparison result when comparing the first operation machine corresponding to the first operation identifier with the second operation machine corresponding to the target identifier; determining a first charging value according to the first operating resource, the first operating machine time and the unit charging value corresponding to the unit resource; comparing the first charging value with the second charging value to obtain a charging value comparison result; and combining the charging resource comparison result and the charging numerical value comparison result to obtain an account checking result.

In one embodiment, the computer program when executed by the processor further performs the steps of: and when the charging state is charging, comparing first resource occupation data corresponding to the first operation identifier with second resource occupation data corresponding to the target identifier, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identifier to obtain a reconciliation result.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A reconciliation data processing method is characterized by comprising the following steps:

2. The reconciliation data processing method of claim 1, wherein the acquiring reconciliation job data comprises:

3. The reconciliation data processing method of claim 2, wherein the comparing the first resource occupation data corresponding to the first job identifier with the second resource occupation data corresponding to the target identifier, and comparing the obtained first charging value with the second charging value corresponding to the target identifier to obtain a reconciliation result comprises:

dividing the first time interval to obtain at least one second time interval;

4. The reconciliation data processing method of claim 3, wherein the performing a reconciliation task comprises:

5. The reconciliation data processing method of claim 1, wherein the comparing the first resource occupation data corresponding to the first job identifier with the second resource occupation data corresponding to the target identifier, and comparing the obtained first charging value with the second charging value corresponding to the target identifier to obtain a reconciliation result, then comprises:

6. The reconciliation data processing method of claim 1 or 5, wherein the first resource occupancy data comprises a corresponding first work resource, first work machine time; the second resource occupation data comprises corresponding second operation resources and second operation machine time;

7. The reconciliation method according to claim 6, wherein each first job identifier comprises at least one corresponding charging switch, and the charging switch is used for identifying a charging state corresponding to the first job identifier, including three states of charging, non-charging and unknown charging state;

8. A reconciliation data processing apparatus, the apparatus comprising:

and the account checking module is used for comparing first resource occupation data corresponding to the first operation identifier with second resource occupation data corresponding to the target identifier, and comparing the obtained first charging numerical value with a second charging numerical value corresponding to the target identifier to obtain an account checking result.

9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.