CN111738733B

CN111738733B - Method and device for processing suspicious account operation

Info

Publication number: CN111738733B
Application number: CN202010552044.0A
Authority: CN
Inventors: 张绪景; 罗东晓; 韦传荣; 王正庚
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2020-06-17
Filing date: 2020-06-17
Publication date: 2024-02-20
Anticipated expiration: 2040-06-17
Also published as: CN111738733A

Abstract

The invention discloses a method and a device for processing suspicious account operation, wherein the method comprises the following steps: acquiring log information of a cross-system job and job success information of a receiver, wherein the log information comprises: program calling exception information; judging whether the job is a suspicious account job or not according to the program call abnormality information in the log information; responding to the judgment result as the suspicious account operation, and judging whether the receiver corresponding to the suspicious account operation is successfully processed according to the receiver operation success information; and responding to the judgment result that the receiving party has successfully processed, and performing compensation processing on the receiving party. The invention can effectively solve the problem of inconsistent cross-system call accounts in time.

Description

Method and device for processing suspicious account operation

Technical Field

The invention relates to the field of data processing, in particular to a method and a device for processing a suspicious account job.

Background

When a banking system calls across application systems, in some cases, such as network delay interruption, abnormality of machines, databases and the like can cause abnormal calling programs, and a calling party does not know whether the called program processes successful account entry or not, and the situation is called as "suspicious account. When the suspicious account occurs, the caller needs to further confirm the problem of accounting consistency generated by the suspicious account and carry out compensation measures. For example, the first party transfers one hundred yuan of civil money to the second party, the second party adds one hundred yuan to the account of the first party, the second party sends instructions to the first party after the account data of the second party is updated, the first party subtracts one hundred yuan from the account after receiving the instructions, and the transaction is completed. If an abnormality occurs, after the account of the second party is added by one hundred yuan, the first party does not receive a determined signal, and at the moment, the first party does not know how to process the account, and the scene is called suspicious account. When the suspicious account occurs, it is necessary to determine whether the account of the party B has been added by one hundred yuan and to perform corresponding processing, otherwise, the financial instability is caused by uneven accounts. The problem of suspicious account brings risks and challenges to the safe operation of a banking system and the maintenance of the stability of a financial market.

The problem of suspicious account is mainly manually judged and intervened at present, namely after the abnormal failure of a calling program, a successful channel log of the called program is checked, and if the successful record is checked to indicate that the other party is processed successfully, compensation (correction) processing is needed. However, the efficiency of manually judging and intervening in the suspicious account is low, so that the problem of inconsistent cross-system call accounts cannot be effectively solved in time.

Disclosure of Invention

In view of the above, the present invention provides a method and apparatus for processing a suspicious account job to solve at least one of the above-mentioned problems.

According to a first aspect of the present invention, there is provided a method of processing a suspicious account job, the method comprising: acquiring log information of a cross-system job and job success information of a receiver, wherein the log information comprises: program calling exception information; judging whether the job is a suspicious account job or not according to the program call abnormal information in the log information; responding to the judgment result as the suspicious account operation, and judging whether the receiver corresponding to the suspicious account operation is successfully processed according to the receiver operation success information; and responding to the judgment result that the receiver has successfully processed, and performing compensation processing on the receiver.

According to a second aspect of the present invention, there is provided an apparatus for processing a suspicious account job, the apparatus comprising: the information acquisition unit is used for acquiring log information of the cross-system job and job success information of a receiver, and the log information comprises: program calling exception information; the suspicious account job judging unit is used for judging whether the job is a suspicious account job or not according to the program call abnormal information in the log information; the receiver processing judging unit is used for responding to the judging result as the suspicious account operation and judging whether the receiver corresponding to the suspicious account operation is successfully processed according to the receiver operation success information; and the compensation processing unit is used for responding to the judgment result that the receiver successfully processes, and carrying out compensation processing on the receiver.

According to a third aspect of the present invention there is provided an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method when the program is executed.

According to a fourth aspect of the present invention there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the above method.

According to the technical scheme, whether the job is the suspicious account job is judged by calling the abnormal information according to the acquired program, when the suspicious account job is judged, whether the corresponding receiver of the suspicious account job is successfully processed is judged according to the successful information of the receiver job, and when the receiver is judged to be successfully processed, the receiver is compensated.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a method of suspicious operation handling according to an embodiment of the present invention;

FIG. 2 is a block diagram of a suspicious operation handling apparatus according to an embodiment of the present invention;

FIG. 3 is an exemplary block diagram of a suspicious operation handling apparatus according to an embodiment of the present invention;

FIG. 4 is a flow chart of the identification of a suspicious account performed by the suspicious account identification unit according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a questionnaire instruction registry according to an embodiment of the invention;

FIG. 6 is a block diagram of a suspicious account background processing unit according to an embodiment of the present invention;

FIG. 7 is a flow chart of a suspicious instructions validation module performing suspicious instructions validation according to embodiments of the present invention;

FIG. 8 is a schematic diagram of a suspicious account instruction to be compensated information table according to an embodiment of the present invention;

FIG. 9 is a flowchart of a suspect account compensation process module performing suspect account compensation according to an embodiment of the present invention;

fig. 10 is a schematic block diagram of a system configuration of an electronic device 600 according to an embodiment of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

Because the existing suspicious account problem is judged and intervened mainly by manpower, the processing efficiency is low, and therefore the problem that the cross-system call accounts are inconsistent can not be effectively solved in time. Based on the above, the embodiment of the invention provides a processing scheme of the suspicious account operation, and discloses a method capable of effectively solving the suspicious account problem from the perspective of a system architecture. Embodiments of the present invention are described in detail below with reference to the accompanying drawings.

FIG. 1 is a flow chart of a method of processing a suspicious operation according to an embodiment of the present invention, as shown in FIG. 1, the method comprising:

step 101, acquiring log information of a cross-system job and job success information of a receiver, wherein the log information comprises: the program calls the exception information.

In actual operation, the account of the system A initiates a transaction (or called a job) to the account of the system B to carry out transfer operation, the transaction can be realized by calling a related program, and the log information in the process of the calling program is the log information of the cross-system job.

The program call abnormality information may be information such as no return, timeout, or communication error.

The receiver job success information indicates transfer success information of an account (e.g., the above-described system B account) that accepts the transfer.

And 102, judging whether the job is a suspicious account job or not according to the program call abnormality information in the log information.

And step 103, responding to the judgment result to be the suspicious account operation, and judging whether the receiver corresponding to the suspicious account operation is successfully processed according to the receiver operation success information.

And 104, in response to the judgment result that the receiver has successfully processed, performing compensation processing on the receiver (for example, the system B account).

By calling the abnormal information according to the acquired program to judge whether the job is the suspicious account job, when the job is judged to be the suspicious account job, judging whether the corresponding receiver of the suspicious account job is successfully processed according to the successful information of the receiver job, and when the job is judged to be the receiver successfully processed, performing compensation processing on the receiver.

For step 103, after the determination result is the suspicious account operation, suspicious account status information may be further set for the suspicious account operation according to a predetermined rule, where the suspicious account status information includes one of the following: to confirm the state, the confirmed state. The predetermined rule here is a rule for setting state information, and may depend on actual operations.

And then judging whether the receiver corresponding to the suspicious account job with the state to be confirmed is successfully processed or not according to the receiver job success information and the preset judging time configuration information.

The determination time configuration information is used to indicate whether the determination operation is performed within a predetermined time, for example, whether the suspicious account job in the state to be confirmed is first processed, if yes, processing is performed, otherwise, whether the suspicious account job in the state to be confirmed is 5 minutes away from the last processing time is determined, and if less than 5 minutes, the suspicious account job in the state to be confirmed is not processed, that is, the determination operation of step 103 is not performed. Therefore, data blocking caused by frequently processing one instruction can be avoided, and the background burden of the system is reduced.

And when the judgment result of the step 104 is that the receiver has successfully processed, updating the suspicious account state information of the suspicious account operation from the state to be confirmed to the confirmed state.

And then, carrying out compensation processing on the sender corresponding to the suspicious account operation according to the preset compensation time configuration information and the compensation frequency threshold value.

The compensation time configuration information is similar to the above-described judgment time configuration information and is also used to indicate whether the compensation operation is performed within a predetermined time.

The compensation frequency threshold value refers to the maximum frequency of compensation operation for the corresponding receiver of the suspicious account operation, and when the maximum compensation frequency is exceeded and the compensation is not successful, the compensation operation is not executed any more, and the subsequent manual processing can be performed.

Based on similar inventive concepts, the embodiment of the present invention further provides a device for processing a suspicious account job, and preferably, the device is used to implement the flow in the above method embodiment.

Fig. 2 is a block diagram showing the construction of the suspicious operation processing apparatus, as shown in fig. 2, the apparatus includes: an information acquisition unit 21, a suspicious account job judgment unit 22, a reception-side processing judgment unit 23, and a compensation processing unit 24, wherein:

an information acquisition unit 21 for acquiring log information of a cross-system job and recipient job success information, the log information including: program calling exception information;

a suspicious account job judging unit 22 for judging whether a job is a suspicious account job or not according to the program call abnormality information in the log information;

a receiver processing judging unit 23, configured to judge whether a receiver corresponding to a suspicious account job has been successfully processed according to the receiver job success information in response to the judging result being the suspicious account job;

and the compensation processing unit 24 is used for performing compensation processing on the receiver if the receiver is successfully processed in response to the judgment result.

The suspicious account job judging unit 22 judges whether the job is the suspicious account job according to the acquired program call abnormal information, when the suspicious account job is judged, the receiver processing judging unit 23 judges whether the receiver corresponding to the suspicious account job is successfully processed according to the receiver job success information, and when the receiver is judged to be successfully processed, the compensation processing unit 24 carries out compensation processing on the receiver.

Specifically, the compensation processing unit may perform compensation processing on the receiver corresponding to the suspicious account job according to the predetermined compensation time configuration information and the compensation frequency threshold.

In one embodiment, the apparatus may further include: a state setting unit configured to set, for the suspicious account job, suspicious account state information according to a predetermined rule, the suspicious account state information including one of: to confirm the state, the confirmed state.

Accordingly, the above-mentioned receiving side processing judging unit is specifically useful for: and judging whether the receiver corresponding to the suspicious account operation in the state to be confirmed is successfully processed or not according to the receiver operation success information and the preset judging time configuration information.

In one embodiment, the apparatus may further include: and the state updating unit is used for updating the suspicious account state information of the suspicious account job from the state to be confirmed to the confirmed state when the judging result of the receiver processing judging unit is that the receiver has successfully processed.

For a better understanding of the present invention, a specific example is given below.

FIG. 3 is an exemplary block diagram of an apparatus for processing a suspicious operation according to an embodiment of the present invention, as shown in FIG. 3, the apparatus including: the cross-system call log acquisition unit 1, the suspicious account identification unit 2 and the suspicious account background processing unit 3 are respectively described in detail below.

The cross-system call log acquisition unit is used for registering logs of cross-system calls, acquiring input and output of programs and important log information during running, wherein the log information is used as a basis for suspicious account identification.

The suspicious account identification unit is used for analyzing and processing the log information obtained by the log acquisition unit and judging whether suspicious accounts appear in the program in the calling process.

Fig. 4 is a flow chart of the suspicious account identification unit, as shown in fig. 4, first, the procedure call log is analyzed, and if the suspicious account record is analyzed as the suspicious account, the suspicious account record is registered in the suspicious account instruction registry, as shown in fig. 5, and the suspicious account state is initialized to 1-suspicious to be confirmed (corresponding to the to-be-confirmed state described above). The unit judges the suspicious account mainly based on whether no return, overtime and specific error code return occur or not when the program is called. If there is no return or timeout when the program is invoked, the network anomaly may be considered to have caused a suspicious account problem, and the transaction is therefore registered as a suspicious account. In addition, if a special error code is returned in the program call, the suspicious account can be judged. For example 4019-gateway communication errors and timeouts 5205-call other procedure errors 96000327-service architecture anomalies. The suspicious account identification unit registers records which generate suspicious accounts as far as possible as suspicious accounts, and after the suspicious account records are registered in a suspicious account instruction register, the suspicious account background can confirm and process each instruction record.

The suspicious account background processing unit is used for starting a timing task in the background, scanning the suspicious account instruction register table registered by the suspicious account identification unit at intervals, and confirming and processing the suspicious account record. As shown in fig. 6, the unit comprises two processing modules: and the suspicious account instruction confirmation module and the suspicious account compensation processing module. These two modules are described separately below.

The function of the suspicious account instruction confirming module is to further confirm and process the suspicious account instruction registered by the suspicious account identifying module, namely confirm whether the called program has been successfully processed by the posting process (i.e. the receiver has been successfully processed). If the called program is successful in accounting processing, setting the suspicious account state as 2-suspicious confirmation, and processing to be compensated (punched positive) if the original transaction is successful; if the called program does not succeed in the posting process, the suspicious account state is set to be 3-suspicious confirmation, and the original transaction does not exist.

In actual operation, confirming whether the invoked program is successfully processed may be accomplished by checking a success channel log of the invoked program, and if a record can be found, confirming that the program has been successfully processed. Generally, when the transaction is successful, the program registers a successful channel log, so that the subsequent check and inquiry are facilitated. In addition, the program accounting processing and the logging success channel log are in one atomic transaction, and the situation that the program processing is successful and the channel log is not logged does not exist.

Fig. 7 is a flow chart of confirmation of the suspicious account instruction executed by the suspicious account instruction confirmation module, as shown in fig. 7, in which the parameter time Ti (corresponding to the judgment time configuration information) is written as a specific time. Firstly, the suspicious account instruction confirming module starts a timing task in the background, scans a suspicious account instruction registry table (see fig. 5) every 30 seconds (time parameter configuration T1), and obtains a suspicious account instruction to be confirmed, namely, a suspicious account instruction with a suspicious account state of 1-suspicious to be confirmed. When the suspicious account instruction to be confirmed is processed, firstly judging whether the last processing time of the suspicious account instruction is 5 minutes (time parameter configuration T2) or not, if the last processing time of the suspicious account instruction is less than 5 minutes (T2), the suspicious account instruction is not processed this time, and the instruction is skipped directly. The purpose of controlling each suspicious account instruction to be processed only once within 5 minutes (time parameter configuration T2) is to avoid data blocking caused by frequently processing one instruction and reduce the background burden of the system. If the last processing is 5 minutes (time configuration T2), the background searches the successful channel log of the called program, if the record is found, the command transaction is successfully checked in, and compensation processing is needed, so that the suspicious account state is updated to be 2-suspicious confirmation, the original transaction is successful, the suspicious account command is to be compensated (flushing processing), the suspicious account command to be compensated information table shown in fig. 8 is registered, and the suspicious account command to be compensated information table is then submitted to a suspicious account compensation processing module for processing. If the found channel log does not exist, further judging whether the registration time of the suspicious account is within 30 minutes (time parameter configuration T3), if so, within T3, considering the delay reason of the successful channel log registration after the successful transaction of the called program, whether the suspicious account instruction is posted cannot be determined temporarily, so that the suspicious account state is not updated, only the processing time stamp field is updated, and the next rescanning confirmation is performed. If the found channel log does not exist and the registration of the suspicious account is beyond 30 minutes (T3), the transaction can be judged to be unsuccessfully checked, so that the state of the suspicious account instruction is updated to be 3-suspicious account confirmation, the original transaction does not exist, and the suspicious account background does not need to carry out compensation processing because the called program is not successfully processed, and the lifecycle of the suspicious account instruction is ended.

And the suspicious account compensation processing module is used for carrying out compensation (flushing) processing on the suspicious account instruction which confirms that the checked-in is successful. The compensation method is to call the compensation service or the reverse service of the corresponding program to restore the accounting data to the state before accounting. For example, the original transaction is to call system B to add 100 elements to account B, then the corresponding compensation process is to call system B to add 100 elements to account B, whereas if the original transaction is to call system B to subtract 100 elements from account B, then the corresponding compensation process is to call system B to add 100 elements to account B.

Fig. 9 is a flowchart of the suspicious account compensation processing module performing suspicious account compensation, and as shown in fig. 9, a time parameter Ti (corresponding to compensation time configuration information) is written as a specific time number in the flowchart. Firstly, the suspicious account compensation processing module starts a timing task in the background, scans a suspicious account instruction to-be-compensated information table shown in fig. 8 every 30 seconds (time parameter T1), and acquires a suspicious account instruction with a state of 1-to-be-compensated processing. When each suspicious account command to be compensated is processed, the control can only be processed once every 5 minutes (time parameter T2), and the compensation is performed for three times, if the compensation is not performed for three times, the background is not processed any more, and the follow-up processing is performed manually. The purpose of such control is to avoid data congestion caused by frequent processing of a suspicious account instruction. As shown in fig. 9, for each suspicious account instruction to be compensated, it is first determined whether the last processing time of the instruction is 5 minutes (time parameter T2) at present, if not, the instruction is not processed this time, and the instruction is skipped. And if the last processing time of the suspicious account instruction is 5 minutes, calling a compensation service (or a reverse service) of the corresponding program to perform compensation processing, and if the compensation processing is successful, updating the compensation state to 2-the compensation processing is successful, wherein the suspicious account instruction compensation processing is completed. If the compensation processing fails, further judging whether the number of times of the compensation processing of the suspicious account instruction is smaller than two times, if so, updating the number of times of the compensation processing, and carrying out the compensation processing next time. If the compensation times are two, the compensation state is directly updated to be 3-the compensation processing fails, manual processing is needed, and the note book is not scanned by the suspicious account background next time. In order to improve the processing efficiency, the suspicious account compensation processing module can only scan suspicious account instructions with the state of 1-to-be-compensated processing.

By the suspicious account operation processing device, automatic identification and automatic compensation of suspicious accounts can be realized, manual intervention is reduced, system call efficiency is improved, and the problem of consistency of cross-system call accounts is effectively solved.

In actual operation, the units and the modules may be combined or may be singly arranged, and the present invention is not limited thereto.

The present embodiment also provides an electronic device, which may be a desktop computer, a tablet computer, a mobile terminal, or the like, and the present embodiment is not limited thereto. In this embodiment, the electronic device may be implemented by referring to the above method embodiment and the embodiment of the suspicious account operation processing apparatus, and the content thereof is incorporated herein, and the repetition is not repeated.

Fig. 10 is a schematic block diagram of a system configuration of an electronic device 600 according to an embodiment of the present invention. As shown in fig. 10, the electronic device 600 may include a central processor 100 and a memory 140; memory 140 is coupled to central processor 100. Notably, the diagram is exemplary; other types of structures may also be used in addition to or in place of the structures to implement telecommunications functions or other functions.

In one embodiment, the suspicious account job handling functionality may be integrated into the central processor 100. Wherein the central processor 100 may be configured to control as follows:

acquiring log information of a cross-system job and job success information of a receiver, wherein the log information comprises: program calling exception information;

judging whether the job is a suspicious account job or not according to the program call abnormal information in the log information;

responding to the judgment result as the suspicious account operation, and judging whether the receiver corresponding to the suspicious account operation is successfully processed according to the receiver operation success information;

and responding to the judgment result that the receiver has successfully processed, and performing compensation processing on the sender corresponding to the suspicious account operation.

As can be seen from the above description, in the electronic device provided in the embodiment of the present application, whether the job is a suspicious account job is determined by calling the anomaly information according to the acquired program, when the suspicious account job is determined, whether the receiver corresponding to the suspicious account job has been successfully processed is determined according to the receiver job success information, and when the receiver is determined to have been successfully processed, the compensation processing is performed on the sender corresponding to the suspicious account job.

In another embodiment, the suspicious account job processing apparatus may be configured separately from the central processing unit 100, for example, the suspicious account job processing apparatus may be configured as a chip connected to the central processing unit 100, and the suspicious account job processing function is implemented by the control of the central processing unit.

As shown in fig. 10, the electronic device 600 may further include: a communication module 110, an input unit 120, an audio processing unit 130, a display 160, a power supply 170. It is noted that the electronic device 600 need not include all of the components shown in fig. 10; in addition, the electronic device 600 may further include components not shown in fig. 10, to which reference is made to the related art.

As shown in fig. 10, the central processor 100, sometimes also referred to as a controller or operational control, may include a microprocessor or other processor device and/or logic device, which central processor 100 receives inputs and controls the operation of the various components of the electronic device 600.

The memory 140 may be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information about failure may be stored, and a program for executing the information may be stored. And the central processor 100 can execute the program stored in the memory 140 to realize information storage or processing, etc.

The input unit 120 provides an input to the central processor 100. The input unit 120 is, for example, a key or a touch input device. The power supply 170 is used to provide power to the electronic device 600. The display 160 is used for displaying display objects such as images and characters. The display may be, for example, but not limited to, an LCD display.

The memory 140 may be a solid state memory such as Read Only Memory (ROM), random Access Memory (RAM), SIM card, or the like. But also a memory which holds information even when powered down, can be selectively erased and provided with further data, an example of which is sometimes referred to as EPROM or the like. Memory 140 may also be some other type of device. Memory 140 includes a buffer memory 141 (sometimes referred to as a buffer). The memory 140 may include an application/function storage 142, the application/function storage 142 for storing application programs and function programs or a flow for executing operations of the electronic device 600 by the central processor 100.

The memory 140 may also include a data store 143, the data store 143 for storing data, such as contacts, digital data, pictures, sounds, and/or any other data used by the electronic device. The driver storage 144 of the memory 140 may include various drivers of the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, address book applications, etc.).

The communication module 110 is a transmitter/receiver 110 that transmits and receives signals via an antenna 111. A communication module (transmitter/receiver) 110 is coupled to the central processor 100 to provide an input signal and receive an output signal, which may be the same as in the case of a conventional mobile communication terminal.

Based on different communication technologies, a plurality of communication modules 110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, etc., may be provided in the same electronic device. The communication module (transmitter/receiver) 110 is also coupled to a speaker 131 and a microphone 132 via an audio processor 130 to provide audio output via the speaker 131 and to receive audio input from the microphone 132 to implement usual telecommunication functions. The audio processor 130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 130 is also coupled to the central processor 100 so that sound can be recorded locally through the microphone 132 and so that sound stored locally can be played through the speaker 131.

The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the suspicious account job processing method described above.

In summary, the cross-system call suspicious account data processing scheme provided by the embodiment of the invention can realize automatic identification and automatic compensation of suspicious accounts, reduce manual intervention, improve system call efficiency and effectively solve the problem of consistency of cross-system call accounts.

Preferred embodiments of the present invention are described above with reference to the accompanying drawings. The many features and advantages of the embodiments are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the embodiments which fall within the true spirit and scope thereof. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the embodiments of the invention to the exact construction and operation illustrated and described, and accordingly, all suitable modifications and equivalents may be resorted to, falling within the scope thereof.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principles and embodiments of the present invention have been described in detail with reference to specific examples, which are provided to facilitate understanding of the method and core ideas of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.

Claims

1. A method of processing a suspicious account job, the method comprising:

judging whether the job is a suspicious account job or not according to the program call abnormal information in the log information; the suspicious account operation is an operation without return, overtime or return of a specific error code;

responding to the judging result as the suspicious account operation, and judging whether the corresponding receiver of the suspicious account operation in the state to be confirmed is successfully processed according to the receiver operation success information and the preset judging time configuration information; the judging time configuration information is used for indicating whether the judging operation is executed within a preset time, and comprises the following steps: if yes, executing processing, otherwise judging whether the suspicious account operation in the state to be confirmed has 5 minutes from the last processing time, and if not, not processing the suspicious account operation in the state to be confirmed;

and responding to the judgment result that the receiver has successfully processed, and performing compensation processing on the receiver.

2. The method of claim 1, wherein in response to determining that the job is a suspicious account job, the method further comprises:

setting suspicious account status information for the suspicious account operation according to a predetermined rule, wherein the suspicious account status information comprises one of the following: to confirm the state, the confirmed state.

3. The method of claim 2, wherein in response to determining that the recipient has successfully processed, the method further comprises:

and updating the suspicious account state information of the suspicious account operation from the state to be confirmed to the confirmed state.

4. The method of claim 2, wherein compensating the recipient comprises:

and carrying out compensation processing on the receiver according to the preset compensation time configuration information and the compensation times threshold value.

5. A device for processing a suspicious account job, the device comprising:

the information acquisition unit is used for acquiring log information of the cross-system job and job success information of a receiver, and the log information comprises: program calling exception information;

the suspicious account job judging unit is used for judging whether the job is a suspicious account job or not according to the program call abnormal information in the log information; the suspicious account operation is an operation without return, overtime or return of a specific error code;

the receiver processing judging unit is used for responding to the judging result as the suspicious account operation and judging whether the receiver corresponding to the suspicious account operation in the state to be confirmed is successfully processed or not according to the receiver operation success information and the preset judging time configuration information; the judging time configuration information is used for indicating whether the judging operation is executed within a preset time, and comprises the following steps: if yes, executing processing, otherwise judging whether the suspicious account operation in the state to be confirmed has 5 minutes from the last processing time, and if not, not processing the suspicious account operation in the state to be confirmed;

and the compensation processing unit is used for responding to the judgment result that the receiver successfully processes, and carrying out compensation processing on the receiver.

6. The apparatus of claim 5, wherein the apparatus further comprises:

a state setting unit configured to set, for the suspicious account job, suspicious account state information according to a predetermined rule, the suspicious account state information including one of: to confirm the state, the confirmed state.

7. The apparatus of claim 6, wherein the apparatus further comprises:

and the state updating unit is used for updating the suspicious account state information of the suspicious account operation from the state to be confirmed to the confirmed state.

8. The apparatus of claim 6, wherein the compensation processing unit is specifically configured to:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any of claims 1 to 4 when the program is executed.

10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 4.